Group Acknowledgement Message Efficiency

ABSTRACT

Techniques for acknowledging communications from multiple devices are described herein. For example, a device may broadcast a group acknowledgement message indicating that communications from multiple devices have been received by the device. Each acknowledgement in the group acknowledgement message may include a device identifier for a device that sent a communication (e.g., a Medium Access Control (MAC) address of the device, a hash of the MAC address of the device, etc.) and a communication identifier for the communication (e.g., a sequence number of the communication, a Cyclic Redundancy Check (CRC) code for the communication, etc.).

RELATED APPLICATION

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 15/395,633, filed on Dec. 30, 2016, the disclosureof which is incorporated by reference herein.

BACKGROUND

Utility meters such as electric, water and gas meters have evolved fromisolated devices that simply measure utility consumption and display aconsumption reading to so called “smart meters” that are connecteddevices capable of reporting resource consumption readings automaticallyover a utility communication network. Some meters, such as electricmeters, are powered by alternating current electricity service (“mainspower”) from the electricity grid. Other devices, such as many water andgas meters, are battery powered. In many cases, such battery powereddevices are expected to operate for extended periods of time (twentyyears or more) without being recharged.

The capabilities of smart meters are continuously growing. Many of theadded capabilities of smart meters come with increased energy demands onthe meter. However, battery technologies have not kept pace with theincreased energy demands. For this reason, battery powered smart metershave not been able to adopt many of the new capabilities that have beenpossible for mains powered devices because doing so would shorten theirbattery life. Consequently, battery powered smart meters have had morelimited functionality than their mains powered counterparts, and havebeen unable to join certain types of communication networks. Otherbattery powered devices have faced similar challenges of increasingfunctionality and communication ability without sacrificing batterylife.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1 is a schematic diagram of an example network architecture.

FIG. 2 is a diagram showing details of an example Full Function Device.

FIG. 3 is a diagram showing details of an example Limited FunctionDevice.

FIG. 4 illustrates an example channel function that may be implementedby a device.

FIG. 5 illustrates an example channel plan.

FIG. 6 illustrates an example structure of a schedule.

FIG. 7 illustrates example schedules.

FIG. 8 illustrates an example sampled listening period associated withan event sampled listening reference point (SLRP).

FIG. 9 illustrates an example process to apply channel data to anoperating context.

FIG. 10 illustrates an example process to generate and send acommunication that includes a channel information element.

FIGS. 11A and 11B illustrate an example process to apply schedule datato an operating context.

FIG. 12 illustrates an example process to generate and send acommunication that includes a schedule information element.

FIG. 13 illustrates an example process to apply seed data to anoperating context.

FIG. 14 illustrates an example process to generate and send acommunication that includes a seed information element.

FIG. 15 illustrates an example process to join a wireless network.

FIG. 16 illustrates an example process to discover a device in awireless network.

FIG. 17 illustrates an example process to determine that a communicationwas received based on a group acknowledgement message.

FIG. 18 illustrates an example process to generate and send a groupacknowledgment message regarding communications from multiple devices.

FIG. 19 illustrates example timing for a discovery process.

FIG. 20 illustrates an example channel information element (CH IE).

FIG. 21 illustrates an example schedule information element (SCH IE).

FIG. 22 illustrates an example Seed Information Element (Seed IE).

FIG. 23 illustrates an example Timing and Type Information Element (TTIE).

FIG. 24 illustrates an example Device Type Information Element (DTypeIE).

FIG. 25 illustrates an example Group Acknowledgment Information Element(GACK IE).

FIG. 26 illustrates an example Load Balancing Information Element (LBIE).

FIG. 27 illustrates an example Directed Network Discovery InformationElement (DND IE).

FIG. 28 illustrates a chart that indicates examples when variousinformation elements may be used.

DETAILED DESCRIPTION

As discussed above, battery powered smart meters and other batterypowered devices have been limited in their ability to provide desiredfunctionality and connectivity without sacrificing battery life. Thisdisclosure describes techniques to minimize the electricity consumptionof limited function devices (e.g., battery powered devices) duringnetwork communications and performance of other functions. Further, thisdisclosure describes other techniques directed to limited functiondevices, full function devices (e.g., mains powered devices), and/orother types of devices. These and other techniques described herein mayallow various devices to perform functions and communicate in ways thatwere not previously possible.

The techniques discussed herein may implement various informationelements to establish communication with limited function devices, fullfunction devices, and/or other types of devices. The informationelements may include reduced amounts of data and/or different data thanthose used in previous techniques. For example, an information elementmay include data that is specific to a channel structure, schedule,seed, timing, and so on. Such information elements may provide aflexible structure for devices to selectively communicate informationthat is needed to establish channel plans or schedules, discoverdevices, acknowledge messages, or facilitate a variety of otherfunctionality. That is, the information elements provide the flexibilityto send some information without sending other information. Further, theinformation elements may be applicable to a wide variety of contexts(e.g., broadcast, multicast, unicast, etc.). In instances where batterypowered devices are implemented, the techniques may, in many instances,minimize battery consumption by communicating less information, incomparison to previous techniques. Further, in instances where aparent-child relationship is implemented, the techniques provide aflexible structure to allow a parent node to control behavior of a childnode(s) (or vice versa), such as establishing a communication schedulefor the child node(s).

In some instances, an information element may reference previous datathat has been sent, instead of including the data in the informationelement. This may minimize data traffic over a network. In one example,a first device may send an information element to a second deviceindicating that data for a first operating context (e.g., a broadcastservice, multicast service, unicast service, etc.) that is alreadyestablished on the second device may be used for a second operatingcontext that has not yet been established on the second device. Thesecond device may then associate the data from the first operatingcontext with the second operating context. To illustrate, a scheduleinformation element may indicate to establish a new broadcast schedulewith schedule data from a unicast schedule that is already establishedon a device.

Further, in some instances an information element may include data toupdate an existing operating context. In one example, a first device maysend an information element to a second device that includes just thedata that is needed to update an operating context that is establishedon the second device. Here, the second device may update the operatingcontext by applying the data from the information element to theoperating context. To illustrate, a channel information element may besent to a device to update a channel plan for an existing unicastschedule that is established for the device. The channel informationelement may include channel data to update the channel plan.

Moreover, in some instances an information element may indicate when toapply data to an operating context. In one example, a first device maysend an information element to a second device requesting that thesecond device update an existing operating context at a particularschedule element in the future (e.g., at a future time). Here, theupdate may be a planned update (i.e., scheduled update). The informationelement may include or reference the data to use for the update. In anyevent, the data may be applied to the existing operating context at theparticular schedule element.

As noted above, the information elements discussed herein may be used toimplement a variety of functionality. In some illustrations, theinformation elements are used to establish communication schedules thatconserve device and/or network resources. For example, a parent devicein a wireless network may communicate with a child device to align thechild device to a particular schedule (e.g., a schedule designated bythe parent device and/or aligned to the parent device). This may allowthe child device to enter a low power state associated with less than athreshold amount of power and awake when a communication is expectedfrom the parent device. In instances where the child device is a batterypowered device, the precise schedule may allow the child device toconserve battery life. Further, if the parent device is associated withmultiple children devices, the parent device may designate separateschedules, or the same schedule, for the children devices. This mayavoid communication collisions and/or unnecessary traffic on thewireless network. Further, such techniques may more efficiently enabledevices to communicate over a network, in comparison to previoustechniques that required a device to track its own timing and timing ofneighboring devices.

Further, in some illustrations the information elements are used todiscover a device within a wireless network in an efficient manner. Forexample, a first device may send a network discovery solicitationmessage to a second device to solicit a communication relationship(e.g., request connection to a parent). In many instances, aparent-child relationship may include a parent routing communicationsfor a child (e.g., downlink communications for the child may be routedthrough the parent and uplink communication from the child may be routedthrough the parent). In many instances, the network discoverysolicitation message may request that such parent-child relationship beestablished. Although in other instances, the network discoverysolicitation message may be sent in other contexts. In any event, thenetwork discovery solicitation may include one or more informationelements that include information regarding a channel plan (e.g., agenerator function associated with the first device, a channel list,etc.), information regarding a schedule of the first device, and/orinformation regarding a listening window during which the first devicewill be listening for communications.

The second device may use a channel function of the first device (whichis based on the channel plan and schedule of the first device) tofrequency hop and send a network discovery message to the first deviceduring the listening window. The network discovery message may includeone or more information elements indicating that the second device maybe used as a parent to the first device. The network discovery messagemay also include an information element to establish a sampled schedulefor the first device moving forward. If the second device is accepted asa parent, the first device may enter a low power state and/or awakestate according to the sampled schedule.

In instances where the first device or the second device is a batterypowered device, this discovery process may conserve battery life. Forexample, by designating a listening window where the first device andthe second device may exchange information the first device and/or thesecond device may avoid constantly communication to establish arelationship. For example, by using a listening window, a device mayavoid waiting relatively long periods of time to communicate withanother device, as was done in previous techniques that use trickletimers. Further, by frequency hopping during the listening window,collisions between communications may be avoided.

Moreover, in some illustrations the information elements are used toacknowledge communications from multiple devices. For example, a devicemay acknowledge that communications from multiple devices have beenreceived, by broadcasting a single group acknowledgement message. Thegroup acknowledgement message may include one or more informationelements that identify a list of acknowledgments. Each of theacknowledgements may include a device identifier for a device that senta communication (e.g., a Medium Access Control (MAC) address of thedevice, a hash of the MAC address of the device, etc.) and acommunication identifier for the communication (e.g., a sequence numberof the communication, a Cyclic Redundancy Check (CRC) code for thecommunication, etc.). The acknowledgements may be formatted in variousmanners, which may be indicated by a type field in the groupacknowledgment message. Acknowledgments of the same type may be groupedtogether.

In some instances, a group acknowledgement message may allow arelatively large number of communications (e.g., hundreds or thousands)to be acknowledged with relatively little information (e.g., a singlemessage). This may be particularly useful for networks that designate adevice to receive communications from many devices (e.g., a starnetwork, etc.). Further, the techniques provide a flexible structurethat allows various data formats to be used (e.g., smaller data formatsin some instances, and larger data formats in others).

In some examples, the techniques may be implemented in the context of anadvanced metering infrastructure (AMI) of a utility communicationnetwork. However, the techniques described herein are not limited to usein a utility industry AMI. For example, the techniques may beimplemented in the context of Distribution Automation, Home EnergyManagement, and so on. Unless specifically described to the contrary,the techniques described herein applicable to any communicationsnetwork, control network, and/or other type of network or system.

In some examples, the techniques are implemented in the context of astandard, such as the Wireless Smart Utility Network (Wi-SUN) standard(e.g., Wi-SUN Field Area Network (Wi-SUN FAN)), IEEE 802.15.4-2015(e.g., wireless mesh network), etc. Further, the techniques may beimplemented in the context of the Internet of Things (IoT). As such, awide variety of devices may be implemented.

By way of example and not limitation, network communication devices(sometimes referred to as nodes, computing devices, or just devices)include utility meters (e.g., electricity, water, or gas meters),relays, repeaters, routers, transformers, sensors, switches,encoder/receiver/transmitters (ERTs), appliances, personal computers(e.g., desktop computers, laptop computers, etc.), mobile devices (e.g.,smartphones, tablets, personal digital assistants (PDAs), electronicreader devices, etc.), wearable computers (e.g., smart watches, opticalhead-mounted displays (OHMDs), etc.), servers, access points, portablenavigation devices, portable gaming devices, portable media players,televisions, set-top boxes, computer systems in an automobile (e.g.,navigation systems), cameras, robots, hologram systems, securitysystems, home-based computer systems (e.g., intercom systems, home mediasystems, etc.), projectors, automated teller machines (ATMs), and so on.In some instances, a network communication device may comprise a batterypowered network communication device (also referred to as a “batterypowered device”) that relies on a battery for power (i.e., is notconnected to mains power). In other instances, a network communicationdevice (also referred to as a “mains powered device”) may comprise amains powered device that relies on mains power for electricity.

Example Environment

FIG. 1 is a diagram illustrating an example networked environment orarchitecture 100. The architecture 100 includes multiple networkcommunication devices. The network communication devices include FullFunction Devices (FFD) 102(1), 102(2), 102(3), 102(4), . . . 102(M)(collectively referred to as “FFDs 102”), and Limited Function Devices(LFDs) 104(1), 104(2), 104(3), . . . 104(N) (collectively referred to as“LFDs 104”), where M and N are any integers greater than or equal to 1and may be the same number or different numbers. In some illustrations,the FFDs 102 include more functionality/resources than the LFDs 104. Inone example, the FFDs 102 are implemented as mains powered devices(MPDs) that are connected to mains electricity (e.g., electricitymeters), while the LFDs 104 are implemented as battery powered devices(BPDs) that are not connected to mains electricity (e.g., water meters,gas meters, etc. that employ batteries). However, in other examples, theFFDs 102 and LFDs 104 may have different processing power, processingcapabilities, and so on. The techniques discussed herein may beimplemented to communicate between FFDs 102, LFDs 104, or anycombination of devices.

The network communication devices are in communication with one anothervia an area network (AN) 106. As used herein, the term “area network”refers to a defined group of devices that are in communication with oneanother via one or more wired or wireless links. Examples of areanetworks include, for example, local area networks (LANs), neighborhoodarea networks (NANs), personal area networks (PANs), home area networks(HANs), Field Area Networks (FANs), or the like. While only one AN 106is shown in FIG. 1, in practice, multiple ANs may exist and maycollectively define a larger network, such as an advanced meteringinfrastructure (AMI) of a utility communication network. At any giventime, each individual device may be a member of a particular AN. Overtime, however, devices may migrate from one AN to another geographicallyproximate or overlapping AN based on a variety of factors, such asrespective loads on the ANs, battery reserves, interference, or thelike.

The term “link” refers to a direct communication path between twodevices (without passing through or being relayed by another device). Alink may be over a wired or wireless communication path. Each link mayrepresent a plurality of channels over which a device is able totransmit or receive data. Each of the plurality of channels may bedefined by a frequency range which is the same or different for each ofthe plurality of channels. In some instances, the plurality of channelscomprises radio frequency (RF) channels. The AN 106 may implement achannel hopping sequence, such that a channel may change over time.Although many examples discussed herein implement a plurality ofchannels as data channels, in some instances the plurality of channelsinclude a control channel that is designated for communicating messagesto specify a data channel to be utilized to transfer data. Transmissionson the control channel may be shorter relative to transmissions on thedata channels.

The AN 106 may comprise a mesh network, in which the networkcommunication devices relay data through the AN 106. Alternatively, oradditionally, the area network 106 may comprise a star network, in whicha central device acts a parent to one or more children devices. Forexample, the FFD 102(M) may act as a parent to the LFDs 104(1), 104(2),and 104(3). Further, in some instances the AN 106 may include a portionthat is implemented as a mesh network and a portion that is implementedas a star network. Moreover, in other instances the AN 106 may beimplemented in whole or part by other types of networks, such ashub-and-spoke networks, mobile networks, cellular networks, etc. In someinstances, a device may be able to communicate with multiple differenttypes of networks (e.g., a mesh network and a star network) at the sameor different times. For instance, if a device is unable to discover asuitable device in a mesh network mode, the device may attempt toconnect to a nearby star network, mobile data collection network, orcellular network. Regardless of the topology of the AN 106, individualnetwork communication devices may communicate by wireless (e.g., radiofrequency) and/or wired (e.g., power line communication, Ethernet,serial, etc.) connections.

In many examples, the LFDs 104 are implemented as leaf nodes. A leafnode may generally communicate with a parent node and not relay data foranother node. As illustrated in FIG. 1, the LFDs 104(1) and 104(2) actas leaf nodes, with the FFD 102(M) being the parent node. However, inother examples the LFDs 104 may relay data for other nodes. Forinstance, the LFD 104(3) may relay data for the LFD 104(N). Further, anytype of device may be implemented as a leaf node (e.g., any of the FFDs102).

The network communication devices also include an edge device 108, whichserves as a connection point of the AN 106 to one or more networks 110(e.g., a backhaul network), such as the Internet. The edge device 108may include, but is not limited to, a field area router (FAR), acellular relay, a cellular router, an edge router, a DODAG (DestinationOriented Directed Acyclic Graph) root, a root device or node of the AN,a combination of the foregoing, or the like. In this illustratedexample, the edge device 108 comprises a FAR, which relays communionsfrom the AN 106 to one or more service providers 112 via the network(s)110.

In some instances, the one or more service providers 112 comprise one ormore central office systems that include a security service such asAuthentication, Authorization and Accounting (AAA) server, a networkregistration service such as Dynamic Host Configuration Protocol (DHCP)server, a network management service (NMS), a collection engine (CE), ameter data management system (in the utility context), a customerrelationship management system (in the sales context), a diagnosticsystem (in a manufacturing context), an inventory system (in a warehousecontext), a patient record system (in the healthcare context), a billingsystem, etc. The network communication devices may register or interactwith some or all of these one or more central office systems. In oneexample, the one or more central office systems may implement a meterdata management system to collect resource consumption data from thenetwork communication devices of the AN 106, process the resourceconsumption data, provide data regarding resource consumption tocustomers, utilities, and others, and/or perform a variety of otherfunctionality. In other instances, the one or more service providers 112comprise other systems to implement other functionality, such as webservices, cloud services, and so on. In yet other instances, the one ormore service providers 112 may be implemented as other types of devices,such as in the context of the Internet of Things (IoT) that allows avariety of devices to exchange data.

The one or more service providers 112 may be physically located in asingle central location, or may be distributed at multiple differentlocations. The one or more service providers 112 may be hosted privatelyby an entity administering all or part of the communications network(e.g., a utility company, a governmental body, distributor, a retailer,manufacturer, etc.), or may be hosted in a cloud environment, or acombination of privately hosted and cloud hosted services.

In many instances, an LFD may connect to a network by connectingdirectly with an FFD. To illustrate, a battery powered water meter, forexample, the LFD 104(1), discovers in its vicinity an electricity meter,the FFD 102(M), connected to mains power. Because the FFD 102(M) isconnected to mains power, it has no practical energy constraints. TheLFD 104(1) may associate the FFD 102(M) as its parent, in which case theFFD 102(M) acts as the connecting point between the LFD 104(1) and theone or more service providers 112.

In other instances, an LFD can connect to a network via an LFD that actsas a relay (an LFD relay). To illustrate, a gas meter, for example, theLFD 104(N), discovers a battery powered water meter, the LFD 104(3),which is already connected to the AN 106 via the FFD 102(M) and can playthe role of an LFD relay. The LFD 104(N) may associate this LFD-relay,the LFD 104(3), as its parent to get connected to the AN 106. In yetfurther instances, an LFD may connect to other networks and/or connectin other manners.

Example Network Communications Devices

FIG. 2 is a diagram showing details of an example Full Function Device200 (FFD) (sometimes referred to as a Mains Powered Device (MPD)). Inthis example, FFD 200 comprises a device that is connected to mainspower, such as an electricity meter, sensor, etc. However, as discussedabove, FFDs can take numerous different forms, depending on the industryand context in which they are deployed. Different types of FFDs may havedifferent physical and/or logical components. For instance, utilitymeter FFDs such as that shown in FIG. 2A may have metrology components,whereas other types of FFDs may not.

As shown in FIG. 2, the example FFD 200 includes a processing unit 202,a transceiver 204 (e.g., radio), one or more metrology devices 206, andan alternating current (AC) power supply 208 that couples to the ACmains power line wherein the FFD 200 is installed. The processing unit202 may include one or more processors 210 and memory 212. When present,the one or more processors 210 may comprise microprocessors, centralprocessing units, graphics processing units, or other processors usableto execute program instructions to implement the functionality describedherein. Additionally, or alternatively, in some examples, some or all ofthe functions described may be performed in hardware, such as anapplication specific integrated circuit (ASIC), a gate array, or otherhardware-based logic device.

The transceiver 204 may comprise one or more hardware and/or softwareimplemented radios to provide two-way RF communication with othernetwork communication devices in the AN 106 and/or other computingdevices via the network 110. The transceiver 204 may additionally oralternatively include a modem to provide power line communication (PLC)communication with other network communication devices that areconnected to an electrical service grid.

The metrology device(s) 206 comprise the physical hardware and sensorsto measure consumption data of a resource (e.g., electricity, water, orgas) at a site of the meter. In the case of an electric meter, forexample, the metrology device(s) 206 may include one or more Hall effectsensors, shunts, or the like. In the case of water and gas meters, themetrology device(s) 206 may comprise various flow meters, pressuresensors, or the like. The metrology device(s) 206 may report theconsumption data to the one or more service providers 112 via thetransceiver 204. The consumption data may be formatted and/or packetizedin a manner or protocol for transmission.

The memory 212 includes an operating system (OS) 214 and one or moreapplications 216 that are executable by the one or more processors 210.The memory 212 may also include one or more metrology drivers 218configured to receive, interpret, and/or otherwise process the metrologydata collected by the metrology device(s) 206. Additionally, oralternatively, one or more of the applications 216 may be configured toreceive and/or act on data collected by the metrology device(s) 206.

The memory 212 may also include one or more communication stacks 220. Insome examples, the communication stack(s) 220 may be configured toimplement a 6LowPAN protocol, an 802.15.4e (TDMA CSM/CA) protocol, an802.15.4-2015 protocol, and/or another protocol. However, in otherexamples, other protocols may be used, depending on the networks withwhich the device is intended to be compatible. The communicationstack(s) 220 describe the functionality and rules governing how the FFD200 interacts with each of the specified types of networks. Forinstance, the communication stack(s) 220 may cause FFDs and LFDs tooperate in ways that minimize the battery consumption of LFDs when theyare connected to these types of networks.

In some instances, the FFD 200 may be configured to send or receivecommunications on multiple channels simultaneously. For example, thetransceiver(s) 204 may be configured to receive data at the same time onhundreds of channels. Additionally, or alternatively, the transceiver(s)204 may be configured to send data at the same time on hundreds ofchannels.

FIG. 3 is a diagram showing details of an example Limited FunctionDevice 300 (sometimes referred to as a Battery Powered Device (BPD). Inthis example, LFD 300 comprises a device that is not connected to mainspower. However, as discussed above, LFDs can take numerous differentforms, depending on the industry and context in which they are deployed.Different types of LFDs may have different physical and/or logicalcomponents. For instance, utility meter LFDs such as that shown in FIG.3 may have metrology components, whereas other types of LFDs may not.

The LFD 300 of FIG. 2 is similar in many respects to the FFD 200. To theextent that the FFD 200 and LFD 300 include the same or similarcomponents, the functions will not be repeated here. Therefore, thefollowing discussion of the LFD 300 focuses on the differences betweenthe LFD 300 and the FFD 200. However, the differences highlighted belowshould not be considered to be exhaustive. One difference between theFFD 200 and the LFD 300 is that the LFD 300 may include a battery 302instead of the AC power supply 208. The specific characteristics of thebattery 302 may vary widely depending on the type of LFD. By way ofexample and not limitation, the battery 302 may comprise a LithiumThionyl Chloride battery (e.g., a 3 volt battery having an internalimpedance rated at 130 Ohms), a Lithium Manganese battery (e.g., a 3volt battery having an internal impedance rated at 15 Ohms), a LithiumIon battery, a lead-acid battery, an alkaline battery, and so on.

Also, in some examples, even components with similar functions may bedifferent for FFDs than for LFDs due to the different constraints. Asone example, while both FFDs and LFDs have transceivers, the specifictransceivers used may be different. For instance, an FFD transceiver mayinclude a PLC modem while an LFD transceiver does not because the LFD isnot connected to an electrical power line that could be used for PLCcommunications. Additionally, or alternatively, an LFD transceiver mayemploy a lower power RF radio to minimize energy consumption. Further,other components of FFDs and LFDs may vary. In some instances, LFDs areimplemented with less functionality and/or include less hardwarecomponents than the FFDs. Further, in some instances components of LFDsare lower power components than the corresponding components of theFFDs.

The memory 212 of the FFD 200 and LFD 300 is shown to include softwarefunctionality configured as one or more “modules.” However, the modulesare intended to represent example divisions of the software for purposesof discussion, and are not intended to represent any type of requirementor required method, manner or necessary organization. Accordingly, whilevarious “modules” are discussed, their functionality and/or similarfunctionality could be arranged differently (e.g., combined into a fewernumber of modules, broken into a larger number of modules, etc.).

The various memories described herein are examples of computer-readablemedia. Computer-readable media may take the form of volatile memory,such as random access memory (RAM) and/or non-volatile memory, such asread only memory (ROM) or flash RAM. Computer-readable media devicesinclude volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage of information suchas computer-readable instructions, data structures, program modules, orother data for execution by one or more processors of a computingdevice. Examples of computer-readable media include, but are not limitedto, phase change memory (PRAM), static random-access memory (SRAM),dynamic random-access memory (DRAM), other types of random access memory(RAM), read-only memory (ROM), electrically erasable programmableread-only memory (EEPROM), flash memory or other memory technology,compact disk read-only memory (CD-ROM), digital versatile disks (DVD) orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other non-transitorymedium that can be used to store information for access by a computingdevice. As defined herein, computer-readable media does not includetransitory media, such as modulated data signals and carrier waves,and/or signals.

While detailed examples of certain computing devices (e.g., the FFD 200and the LFD 300) are described herein, it should be understood thatthose computing devices may include other components and/or be arrangeddifferently. As noted above, in some instances a computing device mayinclude one or more processors and memory storing processor executableinstructions to implement the functionalities they are described asperforming. Certain computing devices may additionally or alternativelyinclude one or more hardware components (e.g., application specificintegrated circuits, field programmable gate arrays, systems on a chip,and the like) to implement some or all of the functionalities they aredescribed as performing. Further, in some examples a computing devicemay be implemented as that described in U.S. application Ser. No.14/796,762, filed Jun. 10, 2015 and titled “Network Discovery by BatteryPowered Devices,” the entire contents of which are incorporated hereinby reference.

By way of example and not limitation, the FFD 200 and/or the LFD 300 mayimplement a variety of modulation techniques and/or data rates, such asfrequency-shift keying (FSK) 802.15.4g (e.g., mandatory mode with a datarate of 50 kbps or 75 kbps, no forward error correction; legacy modewith a data rate of 150 kbps with forward error correction code rate ½;option 2; etc.), offset quadrature phase-shift keying (OQPSK) modulationwith direct-sequence spread spectrum (DSSS) spreading, and so on. Toimplement these different connection modes, a media access control (MAC)sub-layer of a device may be able to indicate to a physical layer themodulation technique and data rate to be used for each transmission.

In many instances, information that is included in an informationelement may be stored in the memory 212 of the FFD 200 and/or the LFD300. For example, the memory 212 may store any information regarding anoperating context, such as schedule data, channel data, seed data,timing data, and so on. In some instances, components of the FFD 200and/or the LFD 300 may reference the information to determine how tocommunicate according to a specific operating context.

Example Channel Function

FIG. 4 illustrates an example channel function 402 that may beimplemented by a device, such as the FFD 200 and/or the LFD 300. In manyinstances, the device may communicate in a frequency hopping context(e.g., dynamic, pseudo-random frequency occupancy). To implementfrequency hopping, the device may employ the channel function 402 todetermine a frequency, at any given time, at which the device willoperate.

As illustrated in FIG. 4, the channel function 402 may rely on multipleelements. In particular, the channel function 402 may depend onfrequencies determined by a channel plan 404 and time determined by aschedule 406. The channel plan 402 may be generated from availablechannels in a channel list 408 and a mapping of the available channelsto a sequence of elements produced by a generator function 410 (e.g., aPseudo-Random Generator Function (PRG)). In some instances, the channellist 408 may exclude channels that are identified in a list of excludedchannels. Different sequences over the same available channels may beproduced depending on a value of a seed 412 that is input into thegenerator function 410. The schedule 406 may be generated based on anactive period 414 and an inactive period 416 for a schedule repetitioninterval 418. The schedule repetition interval 418 may define a durationof time of a schedule element. The active period 414 may define aduration of time within a schedule element during which a device listensfor communications, and the inactive period 416 may define a duration oftime within the schedule element during which the device may not listen.The schedule 406 may define the schedule repetition interval 418 whichmaps onto an element of the channel plan 404 to produce the relationshipbetween time (t) and frequency (f) such that f=C(t). In some instances,the schedule 406 may indicate information related to an event, such as areference schedule element boundary element number (associated with anevent reference schedule element boundary (SEB)), an event offset,and/or an event repetition interval, as discussed in further detailbelow. An example channel plan is discussed in further detail inreference to FIG. 5, while an example schedule structure and schedulesare discussed in reference to FIGS. 6 and 7.

The generator function 410 may implement a variety of functions toproduce the channel plan 404 from the channel list 408. For example, thegenerator function 410 may implement a direct hash (e.g., Jenkins Hash),a randomizing algorithm (e.g., that described in ANSI-TIA-4957.200), orany other type of function.

As such, the channel function 402 may be used by a device to determine afrequency (f) 420 for a time (t) 422. That is, the channel function 420may receive, as an input, the time 422 and provide, as an output, thefrequency 420 for the time 422. This may allow the device to frequencyhop over various channels.

Example Channel Plan

FIG. 5 illustrates an example channel plan 502. The example channel plan502 may be used within the context of the channel function 402 of FIG. 4(e.g., implemented as the channel plan 404).

As illustrated, the channel plan 502 may include a pseudo-random channelnumber sequence (e.g., 21, 13, 46, . . . ). As noted above, a generatorfunction (e.g., the generator function 410 of FIG. 4) may generate thepseudo-random channel number sequence (the channel plan 502) over arange of channel numbers derived from a channel list (e.g., the channellist 408 of FIG. 4). In some instances, the channel list may excludechannels that are identified in a list of excluded channels. In theexample of FIG. 5, each number in the pseudo-random channel numbersequence represents a channel (e.g., a frequency band). As illustrated,a channel plan element 504 may correspond to a channel (e.g., channel 16in this example). Here, there are 128 available channels, although anynumber of channels may be implemented (e.g., 32 channels, 64 channels,etc.). Thus, the pseudo-random channel number sequence may includenumbers from 1 to 128.

In some instances, multiple frequency bands are defined for operation indifferent regions and/or regulatory domains. A total number of channels,and hence the available channel number range, may depend on a selectedregional band and channel spacing, which may be determined by a PHYconfiguration. A channel list may advertise a regional frequency band,channel center frequencies and spacing, and optionally a set of channelsto be excluded.

Example Schedule Structure

FIG. 6 illustrates an example structure of a schedule 600. The schedule600 defines the timing of a sequence of elements superimposed on achannel plan 602. As illustrated, each schedule element in the schedule600 corresponds to a channel plan element in a channel plan 602. Forexample, a schedule element 604 corresponds to a channel plan element606. The schedule 600 describes behavior in the time domain, whereas thechannel plan 602 describes behavior in the frequency domain.

In the example of FIG. 6, an interval between a start of two successiveschedule elements may comprise a Repetition Interval (RI) 608. In otherwords, an RI (also referred to as a “schedule repetition interval”)comprises a duration of time of a schedule element. Each RI begins at aSchedule Element Boundary (SEB) 610. The next SEB occurs on the channelnumber corresponding to the next element in the schedule. The origin ofthe schedule 600 (the SEB of element 0) occurs at a reference time fromwhich the element index corresponding to any given time t can becomputed as Floor((t−SEB₀)/RI). As illustrated, an RI may be composed ofan active period 612 and an inactive period 614. As such, in someinstances, RI=Active Period+Inactive Period. In some instances, theactive period 612 or the inactive period 614 may have a duration of 0seconds.

Example Schedules

FIG. 7 illustrates example schedules 702, 704, 706, and 708. Each of theschedules 702-708 may be associated with a different operating context.For example, the schedule 702 is associated with an FFD broadcastoperating context (e.g., an FFD Broadcast Schedule (BS)), the schedule704 is associated with an FFD unicast operating context (e.g., an FFDUnicast Schedule (US)), the schedule 706 is associated with an LFDbroadcast operating context (e.g., an LFD Broadcast Schedule (BS)), andthe schedule 708 is associated with an LFD unicast schedule (e.g., anLFD Unicast Schedule (US)). As such, each of the schedules 702-708comprises a different schedule type. In some instances, other types ofoperating contexts may additionally be implemented, such as a broadcastschedule operating context associated with group acknowledgment.

An operating context may generally define a set of parameters orinformation for a communication service, such as broadcast, unicast,multicast, etc. For example, an operating context may define a channelplan, a generator function, a channel list, a schedule, an active orinactive period, a schedule repetition interval, a reference scheduleelement boundary element number, an event offset, an event repetitioninterval, a seed value, and so on. In many instances, an operatingcontext may be associated with information included in a channelinformation element, a schedule information element, a timing and typeinformation element, a seed information element, a group acknowledgmentinformation element, and/or any other information element. In someinstances, an operating context may be specific to a device. Forexample, an FFD may include its own broadcast operating context, whilean LFD may include its own broadcast operating context. As discussed infurther detail below, in some instances a parameter or information forone operating context may be used in another operating context. In someinstances, a device may implement multiple operating contexts for thesame type of communication service (e.g., multiple broadcast operatingcontexts).

In one illustration, an operating context may include a generatorfunction, a seed, a channel list, a schedule, an active/inactive period,a repetition interval, and/or event information (e.g., event offset,event repetition interval, etc.). Here, for any given regional frequencyband, a different channel plan may be required for each PHY operatingmode with a different channel list owing to a different channel spacingor different excluded channel list. The generator function (e.g., PRG)can produce different channel plans from the same channel list dependingon the value of the seed. If, for instance, a same generator functionand a same seed value are used, the same channel plan may be determined.The timing defined by the schedule may determine the specific frequencyoccupied at any given time for a specific channel plan. In thisillustration, the schedule may be declared in a schedule informationelement, the generator function and the channel list may be declared ina channel information element, and the seed may either be known a priorior declared in a seed information element. Timing may be defined in atiming and type information element referenced to the Frame ReferenceTime (FRT) (e.g., referenced to some agreed nominal point of the FrameStructure, such as the end of the SHR or the start of the PHR). If noseed information element is included when an operating context isdefined, a MAC address of a device may be used (e.g., an FFD EUI-64).

As noted above, a schedule may include a Repetition Interval (RI) for aschedule element. For example, each element in the FFD BS 702 isassociated with an RI 710, while each element in the FFD US 704 isassociated with an RI 712. In some instances, an element of a schedulemay be associated with an active period and/or an inactive period. Asillustrated, each element in the FFD BS 702 may be associated with anactive period (illustrated without slanted lines) and an inactive period(illustrated with slanted lines). During the active period, the FFD maylisten for broadcast communications from other devices. During theinactive period, the FFD may not listen for broadcast communicationsand/or may perform other functionality, such as transmittingcommunications. Further, each element in the FFD US 704 may comprise anactive period. Here, the FFD may listen for unicast communications fromother devices during the entire element (e.g., the entire RI 712).Moreover, each element in the LFD BS 706 and LFD US 708 may comprise aninactive period. Here, the LFD may not listen for communications, exceptat specific instances (e.g., event SLRPs), as discussed below. In theexample of FIG. 7, the LFD BS 706 and LFD US 708 include the same RI asthe FFD US 704. Although in other examples, the RIs may be different. AnRI may be advertised in a schedule information element.

In many instances, a schedule may be aligned to a specific referencepoint. In the example of FIG. 7, the FFD US 704, the LFD BS 706, and theLFD US 708 are aligned to an Event Reference Schedule Element Boundary(ER SEB) 714. The ER SEB 714 may be at a start of a particular scheduleelement selected to serve as an event reference. For example, a parentFFD may cause children LFDs to be aligned to a schedule that isassociated with the parent FFD. The parent FFD may advertise a referenceschedule element boundary element number to children LFD devices. Thereference schedule element boundary element number may comprise aschedule element number for a particular schedule element selected toserve as an event reference. A start of the particular schedule elementmay comprise the ER SEB. As such, the schedule of the children LFDs maybe aligned to the schedule of the parent FFD. In the example of FIG. 7,the LFD BS 706 and the LFD US 708 are aligned to the FFD US 704. In manyinstances, schedules of children LFDs are aligned to the parent FFDunicast schedule.

As illustrated in FIG. 7, the FFD BS 702 may not be aligned to the ERSEB 714. In some instances, a device may maintain the FFD BS 702 wherethe timing of this schedule drifts with respect to the timing of the FFDUS 704, the LFD BS 706, and the LFD US 708. For example, the FFD BS 702may be maintained using a time derived from a clock local to the device,while the FFD US 704, the LFD BS 706, and/or the LFD US 708 may bemaintained using time derived from a clock of another device. Driftbetween the two clocks may cause the schedule time references (e.g.SEBs) to drift relative each other.

In some instances, a schedule may also include information related to anevent. An event may define a time when a transmission is scheduled tooccur. An event may generally occur at an event Sampled ListeningReference Point (SLRP) (e.g., a time). By defining a time for an eventSLRP, a device may enable or disable a receiver to receive atransmission. Further, the device may enter or awake from a low powerstate. As such, the device may operate in a sampled listening manner.

In the example of FIG. 7, the LFD BS 706 includes Broadcast Event (BE)SLRPs 716 that indicate when the LFD should listen for communications(e.g., for communications from a parent FFD). The first BE SLRP 716(1)may be defined by an Event Offset (EO) 718. As illustrated, the EO 718may comprise a duration of time from the ER SEB 714 to the first BE SLRP716(1). The duration of time may cause the first BE SLRP 716(1) to belocated anywhere within a schedule element (e.g., the BE SLRP 716(1)does not need to be located at the start of a schedule element).Similarly, the LFD US 708 may include an EO 720 from the ER SEB 714 tothe first Unicast Event (UE) SLRP 722(1). As illustrated, the EO 720 maybe different than the EO 718. In instances where a parent FFD managesmultiple children LFDs, this may allow the parent FFD to scheduletransmissions at different times for broadcast and unicast. Although inother instances the EO 720 may be the same as the EO 718.

After a first event SLRP is defined in a schedule, any further eventSLRPs in the schedule may be defined according to an event repetitioninterval. For example, in the LFD BS 706, the BE SLRPs 716 are separatedfrom each other by a BE RI 724. The BE RI 724 may comprise a duration oftime between successive BE SLRPs 716. As also illustrated in the LFD US708, the UE SLRPs 722 are separated from each other by a UE RI 726. Inthis example, the UE SLRPs 722 repeat more frequently than the BE SLRPs716. Although the UE SLRPs 722 may repeat less frequently, or accordingto the same repeat interval. Further, although a particular number ofevent SLRPs are illustrated in FIG. 7 for the LFD BS 706 and/or the LFDUS 708, any number of event SLRPs may be included. Further, the LFD BS706 and/or the LFD US 708 may continue for any length time (e.g., eventSLRPs may repeat according to an event RI for any length of time).

In some instances, a BE SLRPs may be the same for a number of devices.For example, if an FFD acts as a parent for multiple children LFDs, theFFD parent may set a same EO from the ER SEB for the multiple childrenLFDs. Further, the FFD parent may set the same BE RI for the multiplechildren LFDs. This may allow the FFD parent to establish the same BESLRPs, and thus, send a broadcast communication to the multiple LFDchildren at the same time.

Further, in some instances a UE SLRPs may be different for a number ofdevices. In returning to the example where an FFD acts as a parent tomultiple LFDs, the FFD parent may set a different EO from the ER SEB foreach of the multiple children LFDs. Further, the FFD parent may set asame UE RI (or a different UE RI) for each of the multiple children.This may allow the parent FFD to schedule different UE SLRPs (e.g.,unicast transmission at different times) for the different childrenLFDs.

In the example of FIG. 7, the FFD US 704 and LFD BS 706 are shown withidentical channel plans (and schedule elements). In some instances,regulations, such as the Federal Communications Commission (FCC) mayrequire such. However, in other examples the FFD US 704 and LFD BS 706may vary in structure.

In some instances, the schedules 702-708 are described as beingdifferent types due to an association with an active period and/orinactive period. For example, a first type of schedule may be describedas an active period non-zero, zero inactive period schedule (RI=activeperiod). The FFD US 704 is such a schedule. Here, an FFD listens bydefault on the channel corresponding to each element of its US. A secondtype of schedule may be described as an active period non-zero, inactiveperiod non-zero schedule (RI=active period+inactive period). The FFD BS702 is such a schedule. Here, periodically (each RI), an FFD listens onthe channel corresponding to the BS element during the active period anddoes not listen during the inactive period. A third type of schedule maybe described as a zero active period, non-zero inactive period schedule(RI=inactive period). The LFD BS 706 and LFD US 708 (e.g., all LFDschedules) are such in the examples of FIG. 7. Here, an LFD does notlisten on any channel except at specifically defined SLRPs correspondingto events.

Although the schedules 702-708 are illustrated with various items (e.g.,RIs, offsets, event RIs, event SLRPs, etc.), these schedules 702-708 aremerely illustrative. That is, the schedules 702-708 illustrate a fewexample schedules for the purpose of discussion. Many other types ofschedules may be used (e.g., RIs, offsets, event RIs, event SLRPs, etc.may be set to different values), which may depend on the context inwhich the techniques are implement.

Example Sampled Listening Period

FIG. 8 illustrates an example sampled listening period 800 associatedwith an event sampled listening reference point (SLRP) 802. The eventSLRP 802 may correspond to any type of event SLRP, such as the BE SLRP716, EU SLRP 722, and so on.

The sampled listening period 800 may represent a duration of time duringwhich a device listens for a communication defined by an event SLRP. Asnoted above, an event SLRP represents a reference point for a sampledlistening event. For example, an event SLRP indicates when atransmission is scheduled to occur. In some instances, by knowing whenthe event SLRP is, a device may enter a low power state and/or awakefrom the low power state. Since devices may experience clock drift, andtiming inaccuracy, the devices may not be completely synchronized. Thus,the sampled listening period 800 may allow a device to account fortiming uncertainty (e.g., receive a communication even when the device'sclock has drifted with respect to the clock on the other device involvedin the communication).

In particular, the sampled listening period 800 includes a timinguncertainty window 804 located before a Synchronization Header (SHR)capture window 806 and a timing uncertainty window 808 located after theSHR capture window 806. In many instances, the timing uncertainty window804 and the timing uncertainty window 808 may each include the sameduration of time.

As noted above, a device may listen for a communication according to thesampled listening period 800. In particular, the device may enable areceiver to listen (awake from a low power state, in some instances) fora communication at a start 810 of the timing uncertainty window 804.Thereafter, the device may receive the communication during the SHRcapture window 806, and disable the receiver from listening (enter thelow power state, in some instances) at an end 812 of the timinguncertainty window 808. Thus, the device may listen for thecommunication for the duration of the sampled listening period 800.

Example Processes

FIGS. 9-18 illustrate example processes 900, 1000, 1100, 1200, 1300,1400, 1500, 1600, 1700, and 1800 for employing the techniques discussedherein. For ease of illustration the processes 900, 1000, 1100, 1200,1300, 1400, 1500, 1600, 1700, and 1800 may be described as beingperformed by a device described herein, such as the FFD 200 and/or theLFD 300. However, the processes 900, 1000, 1100, 1200, 1300, 1400, 1500,1600, 1700, and 1800 may be performed by other devices. Moreover, thedevices may be used to perform other processes.

The processes 900, 1000, 1100, 1200, 1300, 1400, 1500, 1600, 1700, and1800 (as well as each process described herein) are illustrated alogical flow graph, each operation of which represents a sequence ofoperations that can be implemented in hardware, software, or acombination thereof. In the context of software, the operationsrepresent computer-readable instructions stored on one or morecomputer-readable storage media that, when executed by one or moreprocessors, perform the recited operations. Generally, computer-readableinstructions include routines, programs, objects, components, datastructures, and the like that perform particular functions or implementparticular abstract data types. In some contexts of hardware, theoperations may be implemented (e.g., performed) in whole or in part byhardware logic components. For example, and without limitation,illustrative types of hardware logic components that can be used includeField-programmable Gate Arrays (FPGAs), Application-specific IntegratedCircuits (ASICs), Application-specific Standard Products (ASSPs),System-on-a-chip systems (SOCs), Complex Programmable Logic Devices(CPLDs), etc. The order in which the operations are described is notintended to be construed as a limitation, and any number of thedescribed operations can be combined in any order and/or in parallel toimplement the process. Further, any number of the described operationsmay be omitted.

FIG. 9 illustrates the example process 900 to apply channel data to anoperating context.

At 902, a first device (e.g., the FFD 200 or the LFD 300) may wirelesslyreceive a first communication from a second device (e.g., the FFD 200 orthe LFD 300). The first communication may include a channel informationelement and/or another information element. The channel informationelement may include and/or indicate a tag indicating a first operatingcontext to which to apply channel data; a reference tag including one ormore reference bits to (i) indicate whether the channel data iscontained in the channel information element or has been previouslyreceived and/or (ii) identify a second operating context associated withpreviously received channel data to be used as the channel data; afuture transition element number (e.g., a channel/schedule elementnumber) that indicates when to apply the channel data to the firstoperating context; and/or the channel data. The channel data may includeand/or indicate at least one of a channel plan, a generator function(e.g., Pseudo-Random Generator function (PRG)), a list of channels,and/or a list of excluded channels.

In some instances, the operation 902 is performed without receivingschedule data (e.g., a schedule active period, schedule repetitioninterval, and so on), seed data, etc. Here, the first communication maymerely include or reference channel data to apply to the first context.Although in other instances, such information may be included in thefirst communication.

At 904, the first device may determine whether the channel data iscontained in the channel information element or previously received.This may include analyzing the reference tag of the channel information,which may indicate whether the channel data is contained in the channelinformation element or has been previously received. If the channel datais included in the channel information element, the process 900 mayproceed to 906 to extract the channel data from the channel informationelement. If the channel data has been previously received, the processmay proceed to 908 to access the previously received channel data. Here,the channel data may have been previously stored in memory of the firstdevice (e.g., the memory 212 of the FFD 200 or the memory 212 of the LFD300), and the first device may access that channel data.

Although the process 900 illustrates performing either the operation 906or 908, in some instances both operations may be performed. For example,some channel data may be extracted from the channel information and somechannel data may be accessed from previously received channel data.

In any event, whether channel data is extracted from the channelinformation element and/or accessed from previously stored data, thefirst device may, at 910, apply the channel data to the first operatingcontext. In some instances, the first operating context may have alreadybeen established (e.g., set) on the first device (e.g., channel data mayhave been previously received for the first operating context). Here,the operation 910 may include updating (e.g., replacing) the existingchannel data with the channel data extracted from the channelinformation element or obtained from the second operating context. Assuch, the existing channel data may be updated with the new channeldata. In other instances, the first operating context may not have beenestablished on the first device, and the operation 910 may includeestablishing the first operating context for the first device byassociating the channel data with the first operating context.

If, for example, the future transition element number is specified inthe channel information element, the operation 910 may be performed tothe first operating context at the channel plan or schedule element thatis associated with the future transition element number. To illustrate,the channel data may be applied to a channel plan element that is twentyelements in the future.

At 912, the first device may listen for a second communication and/orsend the second communication based on the first operating context(e.g., the operating context that has the channel data applied thereto).This may include using the channel plan, the generator function, thechannel list, etc. associated with the first operating to listen for orsend the second communication. For example, this may include configuringa radio associated with the first device to operate according to thefirst operating context.

FIG. 10 illustrates the example process 1000 to generate and send acommunication that includes a channel information element.

At 1002, a first device (e.g., the FFD 200 or the LFD 300) may generatea channel information element regarding channel data for a firstoperating context. In some instances, the first device may determine thechannel data to apply to the first operating context and then determinewhether or not a second device has previously received the channel data(e.g., in association with a second operating context). If the seconddevice has received channel data that is determined to be applied to thefirst operating context, the first device may include a reference tag tosignal to the second device to use the previously received channel datafor the first operating context. However, if the channel data has notyet been received, the first device may include the channel data in thechannel information element.

In some instances, if the first device determines that the channel datais to be applied in the future, the first device may include a futuretransition element number in the channel information element.

At 1004, the first device may send a first communication to the seconddevice. The first communication may include the channel informationelement and/or other information elements.

At 1006, the first device may listen for a second communication and/orsend the second communication based on the first operating context andthe channel data referenced or included in the channel informationelement. This may include configuring a radio of the first device tooperate according to the first operating context with the channel datahaving been applied thereto.

FIGS. 11A and 11B illustrate the example process 1100 to apply scheduledata to an operating context.

In FIG. 11A, at 1102, a first device (e.g., the FFD 200 or the LFD 300)may wirelessly receive a first communication from a second device (e.g.,the FFD 200 or the LFD 300). The first communication may include aschedule information element. The schedule information element mayinclude and/or indicate a tag indicating a first operating context towhich to apply schedule data; a reference tag including one or morereference bits to (i) indicate whether at least a portion of theschedule data is contained in the schedule information element or hasbeen previously received and/or (ii) identify a second operating contextassociated with a previously received schedule data to be used as atleast the portion of the schedule data; a future transition elementnumber that indicates when to apply the schedule data to the firstoperating context; and/or the schedule data.

The schedule data may include and/or indicate a schedule active periodcomprising a duration of time of an active period within a scheduleelement during which the first node listens for communications; aschedule repetition interval comprising a duration of time of theschedule element; an event reference comprising a reference scheduleelement boundary element number for a particular schedule element, astart of the particular schedule element comprising an event referenceschedule element boundary (SEB); an event offset comprising a durationof time from the event reference SEB to an event sampled listeningreference point (SLRP); and/or an event repetition interval comprising aduration of time between successive event SLRPs.

In some instances, the reference tag is used to reference a particulartype of schedule data. For example, the reference tag may be used toreference a previously established schedule active period or apreviously established schedule repetition interval. As such, a portionof the schedule data may include the previously established scheduleactive period or a previously established schedule repetition interval,in some instances. Although in other instances, the reference tag mayreference any type of schedule data.

In some instances, the operation 1102 is performed without receivingdata indicating a channel plan, a generator function, a list ofavailable channels, a list of excluded channels, or other channel data.In other words, the first communication may not include such data (e.g.,may not include channel data). Here, the first communication may merelyinclude or reference schedule data to apply to the first context.Although in other instances, such information may be included (e.g., ina channel information element).

At 1104, the first device may determine whether or not at least aportion of the schedule data is contained in the schedule informationelement. For example, the first device may analyze the reference tag,which may indicate whether or not at least the portion of the scheduledata is contained in the schedule information element. If at least theportion of the schedule data is contained in the schedule informationelement (e.g., the YES path), the process 1100 may proceed to 1106 andextract at least the portion of the schedule data from the scheduleinformation element. If at least the portion of the schedule data is notcontained in the schedule information element (e.g., the NO path), theprocess 1100 may skip the operation 1106.

At 1108, the first device may determine whether or not at least aportion of the schedule data was previously received. In other words,the first device may determine whether or not at least the portion ofthe schedule data is associated with an existing operating contextestablished on the first device (e.g., the second operating context). Ifat least a portion of the schedule data was previously received (e.g.,the YES path), the process 1100 may proceed to 1110 and access at leastthe portion of the previously received schedule data. Here, thepreviously received schedule data may have been previously stored inmemory of the first device (e.g., the memory 212 of the FFD 200 or thememory 212 of the LFD 300), and the first device may access thatschedule data from the memory. If at least the portion of the scheduledata was not previously received (e.g., the NO path), the process 1100may skip the operation 1110.

In any event, at 1112, the first device may apply the schedule data thatis extracted and/or accessed from previously received schedule data tothe first operating context. In some instances, the first operatingcontext may have already been established (e.g., set) on the firstdevice (e.g., schedule data may have been previously received for thefirst operating context). Here, the operation 1112 may include updating(e.g., replacing) the existing schedule data with the schedule dataextracted from the schedule information element and/or obtained from thesecond operating context (e.g., the memory of the first device). Assuch, the existing schedule data may be updating with the new scheduledata. In other instances, the first operating context may not have beenestablished on the first device, and the operation 1112 may includeestablishing the first operating context for the first device byassociating the schedule data with the first operating context.

If, for example, the future transition element number is specified inthe schedule information element, the operation 1112 may be performed tothe first operating context at the channel plan or schedule element thatis associated with the future transition element number. For example,the schedule data may be applied to a channel plan element that istwenty elements in the future.

In FIG. 11B, at 1114, the first device may determine a schedule for thefirst operating context. That is, the schedule may be based on the firstoperating context with the schedule data applied. The schedule mayindicate various information, as discussed herein. For example, theschedule may indicate an event reference schedule element boundary, anevent offset to a first event Sampled Listening Reference Point (SLRP),an event repetition interval, and so on. As such, the schedule maygenerally indicate when a communication is expected to be transmittedfrom another device. In many instances, this may allow the first deviceto determine when it needs to be awake and where to listen for acommunication (e.g., on what channel).

At 1116, the first device may determine a listening period (e.g.,sampled listening period). This may include determining a particularamount of time before an event SLRP and/or a particular amount of timeafter the event SLRP. The listening period may be determined based on alast communication that was received from the second device (e.g., aparent device to which the first device is synchronized), where the lastcommunication includes timing synchronization information (e.g.,information in a timing and type information element); an amount of timethat has lapsed since receiving the last communication from the seconddevice; an amount of timing uncertainty associated with the firstdevice, where the timing uncertainty is based on a timing accuracy forthe first device (e.g., jitter) or clock drift for the first device(e.g., how accurate is the clock of the first device); and/or an amountof timing uncertainty associated with the second device, where thetiming uncertainty is based on a timing accuracy for the second node(e.g., jitter) or clock drift for the second node (e.g., how accurate isthe clock of the second device). In some instances, timingsynchronization information is included in each communication that issent. In one illustration, the listening period may increase (ordecrease) as the amount of time from receiving a last communication thatincludes timing synchronization information increases (or decreases). Inanother illustration, the listening period may increase (or decrease) asthe amount of timing uncertainty of the first device or the seconddevice increases (or decreases). In yet other illustrations, anycombination of such techniques may be implemented to increase ordecrease the listening period.

At 1118, the first device may place the first device in a low powerstate based on the schedule and/or the listening period. The low powerstate may comprise a sleep state, an off state, or any other state thatis associated with less than a threshold amount of power (e.g., thefirst device is consuming less than the threshold amount of power). Whenthe first device is fully powered on and/or not asleep, the first devicemay be associated with more than the threshold amount of power (e.g.,the first device is consuming more than the threshold amount of power).

At 1120, the first device may awake from the low power state based onthe schedule and/or the listening period. For example, the first devicemay awake from the low power state at the start of the listening periodassociated with an event SLRP.

At 1122, the first device may listen for a second communication duringthe listening window.

The operations 1118, 1120, and/or 1122 may generally be implemented tomaintain the first device in the low power state for as long aspossible. This may conserve battery life, processing resources, etc. Forexample, the first device may be placed in the low power state for anyperiod of time where a transmission event is not scheduled to occur. Toillustrate, during an event repetition interval (between event SLRPs)the first device may remain in a low power state. The first device mayawake just before an event SLRP (at the start of the listening period)to listen for a communication. After the listening period has expired,the first device may return to the low power state.

FIG. 12 illustrates the example process 1200 to generate and send acommunication that includes a schedule information element.

At 1202, a first device (e.g., the FFD 200 or the LFD 300) may generatea schedule information element regarding schedule data for a firstoperating context. In some instances, the first device may determine theschedule data to apply to the first operating context and then determinewhether or not a second device has previously received the schedule datafor a second operating context. If the second device has receivedschedule data that is determined to be applied to the first operatingcontext, the first device may include a reference tag to signal to thesecond device to use the previously received schedule data for the firstoperating context. However, if the schedule data has not yet beenreceived, the first device may include the schedule data in the scheduleinformation element.

In some instances, if the first device determines that the schedule datais to be applied in the future, the first device may include a futuretransition element number in the schedule information element.

At 1204, the first device may send a first communication to the seconddevice. The first communication may include the schedule informationelement and/or other information elements.

At 1206, the first device may listen for a second communication and/orsend the second communication based on the first operating context andthe schedule data referenced or included in the schedule informationelement. This may include configuring a radio of the first device tooperate according to the first operating context with the schedule datahaving been applied thereto.

In some instances, the process 1200 may allow the first device tocontrol a schedule of the second device. For example, the first devicemay act as a parent to multiple children devices. The parent device maydetermine unicast schedules for the children devices that indicate thatthe parent device will send unicast communications at different times.Here, the parent device may send schedule data regarding the unicastschedules to the children devices in schedule information elements. Eachschedule information element may identify the same event reference SEB,but provide a different offset. This may synchronize the childrendevices to the event reference SEB. Further, this may provide differenttimes for the parent device to send unicast communications to thechildren devices. Additionally, or alternatively, the parent device mayschedule the children devices to receive broadcast communications at thesame time. The parent device may send schedule data regarding thebroadcast schedules to the children devices in schedule informationelements. Each schedule information element may identify the same eventreference SEB and provide the same offset. The schedule informationelements for the broadcast schedules may be sent at the same time as theschedule information elements for the unicast schedules and/or atdifferent time. As such, the parent device may efficiently schedulecommunications with the children devices (e.g., to avoid communicationcollisions, etc.).

Further, in some instances a parent device may determine an eventrepetition interval based on timing uncertainty of multiple childrendevices. For example, the parent device may determine the eventrepetition interval (for a specific child device or across all childrendevices) to be shorter than a period of time it takes for a device tofall out of synchronization. To illustrate, if a child device drifts outof synchronization relatively quickly (e.g., over less than a period oftime), the parent device may set the event repetition interval to berelatively short. This may allow communications to be received by thechild device and remain in sync. In other instances, a parent device maycontrol schedules for children devices in other manners (e.g., set othertypes of schedules).

FIG. 13 illustrates the example process 1300 to apply seed data to anoperating context.

At 1302, a first device (e.g., the FFD 200 or the LFD 300) maywirelessly receive a first communication from a second device (e.g., theFFD 200 or the LFD 300). The first communication may include a seedinformation element and/or another information element. The seedinformation element may include and/or indicate a seed tag indicating afirst operating context to which to apply seed data; a seed referencetag including one or more seed reference bits to (i) indicate whetherthe seed data is contained in the seed information element or has beenpreviously received and/or (ii) identify a second operating contextassociated with previously received seed data to be used as the seeddata; a future transition element number that indicates when to applythe seed data to the first operating context; and/or the seed data. Theseed data may indicate a seed value to input into a generator function.

At 1304, the first device may determine whether the seed data iscontained in the seed information element or has been previouslyreceived. This may include analyzing the seed reference tag, which mayindicate whether the seed data is contained in the seed informationelement or has been previously received. If the seed data is included inthe seed information element, the process 1300 may proceed to 1306 toextract the seed data from the seed information element. If the seeddata has been previously received, the process may proceed to 1308 toaccess the previously received seed data. Here, the seed data may havebeen previously stored in memory of the first device (e.g., the memory212 of the FFD 200 or the memory 212 of the LFD 300), and the firstdevice may access that seed data.

In any event, whether the seed data is extracted from the seedinformation element or accessed from previously stored data, the firstdevice may, at 1310, apply the seed data to the first operating context.In some instances, the first operating context may have already beestablished (e.g., set) on the first device (e.g., seed data may havebeen previously received for the first operating context). Here, theoperation 1310 may include updating (e.g., replacing) the existing seeddata with the seed data extracted from the seed information element orobtained from the second operating context. As such, the existing seeddata may be updated with the new seed data. In other instances, thefirst operating context may not have been established on the firstdevice, and the operation 1310 may include establishing the firstoperating context for the first device by associating the seed data withthe first operating context.

If, for example, the future transition element number is specified inthe seed information element, the operation 1310 may be performed to thefirst operating context at the channel plan or schedule element that isassociated with the future transition element number. For example, theseed data may be applied to a channel plan element that is twentyelements in the future.

FIG. 14 illustrates the example process 1400 to generate and send acommunication that includes a seed information element.

At 1402, a first device (e.g., the FFD 200 or the LFD 300) may generatea seed information element regarding seed data for a first operatingcontext. In some instances, the first device may determine the seed datato apply to the first operating context and then determine whether ornot a second device has previously received the seed data for a secondoperating context. If the second device has received seed data that isdetermined to be applied to the first operating context, the firstdevice may include a reference tag to signal to the second device to usethe previously received seed data for the first operating context.However, if the seed data has not yet been received, the first devicemay include the seed data in the seed information element.

In some instances, if the first device determines that the seed data isto be applied in the future, the first device may include a futuretransition element number in the seed information element.

At 1404, the first device may send a first communication to the seconddevice. The first communication may include the seed information elementand/or other information elements.

At 1406, the first device may listen for a second communication and/orsend the second communication based on the first operating context andthe seed data referenced or included in the seed information element.This may include configuring a radio of the first device to operateaccording to the first operating context with the seed data having beenapplied thereto.

A channel information element, schedule information element, seedinformation element, and/or any other information element discussedherein may be sent and/or received at various instances. For example,any information element may be communicated during discovery, PersonalArea Network (PAN) configuration (e.g., detailing PAN specificinformation, such as active security key information, PAN broadcastschedule and channel information, configuration sequence number (toidentify when the configuration information has changed), etc.), a PANconfiguration update, a channel update process to update channel data(e.g., a channel plan), a schedule update process to update scheduledata (e.g., a schedule), a seed update process to update seed data, agroup acknowledgment message, etc. As such, the processes 900, 1000,1100, 1200, 1300, and/or 1400 may be performed at a variety of times.

Further, although the processes 900, 1000, 1100, 1200, 1300, and/or 1400are discussed as including one information element, any number ofinformation elements may be included. In one example, multiple channelinformation elements may be included in a single communication to updatemultiple operating contexts. In another example, multiple scheduleinformation elements may be included in a single communication to updatemultiple operating contexts. In yet a further example, a channelinformation element(s), a schedule information element(s), and a seedinformation element(s) may be included in a same communication.

FIG. 15 illustrates the example process 1500 to join a wireless network.For ease of illustration, the process 1500 is discussed in the contextof being performed by a Limited Function Device (LFD), such as the LFD300. For example, the process 1500 may be performed by an LFD desiringto associate to a parent device (e.g., establish a relationship forcommunications in the future). However, the process 1500 may beperformed in other contexts and/or by other devices.

At 1502, the LFD may send a network discovery solicitation message tocreate a communication relationship. The network discovery solicitationmessage may be sent over multiple channels of a wireless network, suchas all available channels. The network discovery solicitation messagemay request to create a communication relationship with a parent. Thenetwork discovery solicitation message may include a channel informationelement indicating a channel list and a generator function that isimplemented by the LFD (e.g., information regarding a channel plan), aschedule information element including schedule data regarding aschedule of the LFD, a timing and type information element describing acurrent location in the schedule, a seed information element indicatinga seed value to input into the generator function, a directed networkdiscovery information element indicating a listening window, and so on.

At 1504, the LFD may listen, while frequency hopping during thelistening window, for a network discovery message. The frequency hoppingmay be based on the channel list and the generator function that isimplemented by the LFD, the schedule data regarding the schedule of theLFD, the timing information in the timing and type information element,and/or the seed value indicated in the network discovery solicitationmessage. In other words, the LFD may implement the generator functionover the channel list, the schedule data, the timing information, and/orthe seed data that was advertised at 1502 to frequency hop during thelistening window. A device desiring to communicate with the LFD may alsobe frequency hopping during the listening window based on the same data.By exchanging information regarding the channel function, the LFD and anFFD may frequency hop during the listening window while the devices areestablishing a communication relationship. In many instances, thelistening window may comprise a relatively short period of time, such asless than 10 minutes, less than 5 minutes, less than 1 minute, etc.

At 1506, the LFD may receive, during the listening window, a networkdiscovery message from a FFD. The network discovery message may that theFFD is able to serve as a parent node for the LFD. The network discoverymessage may be received as a unicast communication from the FFD. Thenetwork discovery message may include data for any number of operatingcontexts, such as a predetermined number of operating contexts, alloperating context that the LFD will use going forward, a singleoperating context, etc. For example, the network discovery message mayinclude a channel information element indicating a channel list and agenerator function that is implemented by the FFD (or that the FFDrequests that the LFD use), a schedule information element includingschedule data regarding a schedule of the FFD (or that the FFD requeststhat the LFD use), a timing and type information element describing acurrent location in the schedule, a seed information element indicatinga seed value to input into the generator function, and so on. In manyinstances, the network discovery message may enable the FFD to control acommunication schedule of the LFD for a given operating context. Toillustrate, the network discovery message may specify data for abroadcast operating context, data for a unicast operating context, datafor a multicast operating context, and so on. Although, in manyinstances, the data regarding the broadcast operating context isprotected and is not provided until after authentication has occurred.

In some instances, the network discovery message may include loadbalancing information regarding the FFD. The load balancing informationmay indicate an amount of load on the FFD. The amount of load may bebased on a number of children devices (e.g., LFDs) that are supported bythe FFD, a processor load of the FFD (e.g., an average processor load, acurrent processor load, etc.), and/or a radio load of the FFD (e.g., howmuch of the time the radio is being used). The amount of load maycomprise a value (e.g., on a scale of 1 to 10), a percentage (e.g., apercentage of full capacity), a classification (e.g., no load, someload, normal load, very busy, etc.).

At 1508, the LFD may select an FFD to act as a parent. For example, ifthe LFD receives network discovery messages from multiple neighboringFFDs, the LFD may select a particular FFD to act as a parent device forfuture communication. In some instances, the LFD may select an FFD basedon load balancing information from each FFD that sends a networkdiscovery message and/or a strength of a communication link between theLFD and the respective FFD. In one illustration, the LFD may select anFFD to act as a parent when the strength of the link between the LFD andthe FFD is greater than a threshold and/or the FFD is associated withless than a particular amount of load. In other illustrations, an FFDmay be selected in other manners.

In some instances, the selected FFD may control the rate at whichcommunications are exchanged initially and then update that rate fornormal communications after the initial exchange. For example, during adiscovery process and/or authentication process, where manycommunications may be exchanged to establish normal operatingconditions, the FFD may cause the FFD and LFD to exchange communicationsrelatively frequently (e.g., by sending a message that specifies arelatively short event repetition interval). After authentication datais exchanged (e.g., encryption keys, so that the devices can communicatein a secure manner), the FFD may send a message that specifies a newevent repetition interval. At 1510, the LFD may receive the message withthe new event repetition interval, causing communications going forwardto be exchanged less frequently (e.g., by sending a message thatspecifies a relatively long event repetition interval). However, inother instances the FFD may cause initially communications to beexchanged infrequently, and frequently thereafter.

At 1512, the LFD may determine a sampled communication schedule based onthe information in the network discovery message (e.g., channel data,schedule data, seed data, etc.). The sampled communication schedule maycomprise any of the schedules discussed herein, such as a schedule shownin FIG. 7. The sampled communication schedule may generally indicatethat the LFD may periodically listen for communications. For example,the schedule may include event SLRPs defined by an event offset and anevent repetition interval.

At 1514, the LFD may communicate based on the sampled communicationschedule. For example, the LFD may be placed in a low power stateassociated with less than a threshold amount of power during periods oftime when communications are not expected to be transmitted to the LFD.The LFD may awake from the low power state to listen for a communicationat an event SLRP (e.g., at the start of a listening period). Thelistening may be based on an operating context that was made known tothe LFD during the process 1500 (e.g., by the network discoverymessage).

FIG. 16 illustrates the example process 1600 to discover a device in awireless network. For ease of illustration, the process 1600 isdiscussed in the context of being performed by a FFD, such as the FFD200. For example, the process 1600 may be performed by an FFD thatreceives a communication from an LFD desiring to associate to with theFFD as a parent device. However, the process 1600 may be performed inother contexts and/or by other devices.

At 1602, the FFD may receive a network discovery solicitation messagefrom an LFD to create a communication relationship. The networkdiscovery solicitation message may request to create a communicationrelationship with the FFD as a parent. The network discoverysolicitation message may include a channel information elementindicating a channel list and a generator function that is implementedby the LFD, a schedule information element including schedule dataregarding a schedule of the LFD, a timing and type information element,a seed information element indicating a seed value to input into thegenerator function, a directed network discovery information elementindicating a listening window, and so on.

At 1604, the FFD may determine an amount of load on the FFD. The amountof load may be based on a number of children nodes that are supported bythe FFD, a processor load on one or more processors of the FFD over aperiod of time, and/or a radio load on a radio of the FFD over theperiod of time.

At 1606, the FFD may determine to attempt to create a communicationrelationship. For example, if an amount of load on the FFD is less thana threshold, the FFD may determine that it can serve as a parent to theLFD. Additionally, or alternatively, the FFD may base the determinationon a strength of a connection between the FFD and the LFD.

At 1608, the FFD may generate a network discovery message. This mayinclude determining information for a channel information element,schedule information element, timing and type information element, seedinformation element, and so on for an operating context to beimplemented by the LFD. The network discovery message may include theseinformation elements, as well as other information elements. In someinstances, the network discovery message includes load balancinginformation indicating an amount of load on the FFD.

At 1610, the FFD may frequency hop during the listening window based onthe generator function that is implemented by the LFD and/or any otherinformation that is provided by the LFD in the network discoverysolicitation message.

At 1612, the FFD may select a random time during the listening window tosend the network discovery message. This may avoid communicationcollisions with other FFDs that may be attempting to communicate withthe LFD.

At 1614, the FFD may send, during the listening window, the networkdiscovery message. The message may be sent at the random time selectedat 1612. In many instances, the network discovery message is sent as aunicast message directly to the LFD.

Thereafter, the FFD and the LFD may communicate according to theinformation in the network discovery message.

In some instances, as noted above, the FFD may control the rate at whichcommunications are exchanged initially and then update that rate fornormal communications after the initial exchange. In such instances, theFFD may send, at 1616, a new event repetition interval for communicatingwith the FFD. The new event repetition interval may be sent afterinitial communications are exchanged (e.g., after authentication data isexchanged).

FIG. 17 illustrates the example process 1700 to determine that acommunication was received based on a group acknowledgement message.

At 1702, a first device (e.g., the FFD 200 or LFD 300) may send a firstcommunication to a second device (e.g., the FFD 200 or LFD 300) inwireless network. The first communication may include any type of acommunication that is generally acknowledged by a receiving device.

At 1704, the first device may receive a group acknowledgement messagefrom the second device. The group acknowledgment message may comprise asingle message to acknowledge that communications from multiple deviceswere received at second device. The group acknowledgement message mayhave been sent as a broadcast to the first device and at least one otherdevice.

The group acknowledgement message may generally include acknowledgmentsfor communications from multiple devices. An acknowledgment may includea device identifier for a device that sent a communication (e.g., aMedium Access Control (MAC) address of the device, a hash of the MACaddress of the device, etc.) and a communication identifier for thecommunication (e.g., a sequence number of the communication, a CyclicRedundancy Check (CRC) code for the communication, etc.). In manyinstances, the group acknowledgment message may include a type field toindicate a type of acknowledgments in a list, a number field to indicatea number of the acknowledgements in the list, and a list field thatincludes the acknowledgements in the list. If multiple types ofacknowledgments are included in the group acknowledgment message, theacknowledgments may be grouped by type.

At 1706, the first device may determine that the first communication wasreceived at the second device. This may include analyzing the groupacknowledgment message to determine if a communication identifier forthe first communication and/or a device identifier for the first deviceis included in the group acknowledgment message. Since a communicationidentifier may not be unique across all messages, the analysis may lookfor the communication identifier in association with the deviceidentifier.

In some instances, the group acknowledgment message may indicate astrength of a received communication (e.g., RSL value). In some of theseinstances, the first device may use this information to adjust an uplinkcommunication, at 1708. For example, if the RSL value is below athreshold, the first device may switch to another parent device, changea power level for transmitting, and so on.

FIG. 18 illustrates the example process 1800 to generate and send agroup acknowledgment message regarding communications from multipledevices.

In some instances, a device identifier may include a hash of a MACaddress or other data. On occasion, a first hash of a MAC address of afirst child device (a first device identifier) and a second hash of aMAC address of a second child device (a second device identifier) resultin the same value (e.g., the first device identifier and the seconddevice identifier are the same value). If the first hash and the secondhash were included in a group acknowledgment, the first child device andthe second child device may not know which device is being acknowledged,since the acknowledgments may be the same.

As such, when a first device (e.g., the FFD 200 or the LFD 300) isassociated with children devices, the first device may, at 1802, analyzeinformation of the children devices to determine a type ofacknowledgement to use. For example, if the first device determines thata hash of a MAC address for a first child device (e.g., a short deviceidentifier for the first child device) is the same as a hash of a MACaddress for a second child device (e.g., a short identifier for thesecond child device), the first device may determine to use a longerdevice identifier for acknowledgements (e.g., a type of acknowledgmentthat includes more data), such as a full MAC address. This may avoidconflicting acknowledgments (e.g., acknowledgments that include the sameinformation). In some instances, the operation 1802 is performed beforecommunications are received from the children devices. In otherinstances, the operation 1802 is performed when communications arereceived. In yet other instances, the operation 1802 may not beperformed.

At 1804, the first device may receive a first communication from asecond device, such as from a second child device.

At 1806, the first device may receive a second communication from athird device, such as a third child device. The first communicationand/or the second communication may each comprise a type ofcommunication that is generally acknowledged by a receiving device.

At 1808, the first device may generate a group acknowledgment messageregarding the first communication and the second communication. Thegroup acknowledgment message may acknowledge receipt of the firstcommunication and the second communication at the first device. As notedabove, in many instances the group acknowledgment message may include atype field to indicate a type of acknowledgments in a list, a numberfield to indicate a number of the acknowledgements in the list, and alist field that includes the acknowledgements in the list. In someinstances, the group acknowledgment includes acknowledgments of aparticular type (e.g., a long device identifier when short deviceidentifiers for children devices are the same value). Further, in someinstances the group acknowledgement message may indicate a signalstrength of receiving the first communication (e.g., RSL) and/or asignal strength of receiving the second communication.

At 1810, the first device may send the group acknowledgement message.The group acknowledgment message may be sent as a broadcast to thesecond device, the third device, and/or any other devices that may bewithin communication range of the first device. That is, the groupacknowledgment message may include a single message that is transmittedas a broadcast to multiple devices (in some instances, hundreds ofdevices).

Example Discovery Process

FIG. 19 illustrates example timing for a discovery process 1900. Theprocess 1900 may be performed when a device desires to join a network(e.g., establish a parent-child relationship with another device). Forease of illustration, the process 1900 will be discussed in the contextof an LFD and multiple FFDs. However, the process 1900 may be performedby other devices.

As illustrated, the process 1900 is associated with Network DiscoverySolicitation (NDS) windows 1902(1), 1902(2), 1902(3), . . . 1902(P) anda Network Discovery (ND) listening window 1904. Each of the NDS windows1902 and the ND listening window 1904 are separated by gaps 1906(1),1906(2), 1906(3), . . . 1906(R−1), and 1906(R), such as Short InterframeSpacings (SIFSs). The ND listening window 1904 may be referred to as aresponse period, in some instances.

During the NDS windows 1902, an LFD may send Network DiscoverySolicitation (NDS) messages requesting a communication relationship withan FFD. Any number of NDS messages may be sent before the ND listeningwindow 1904 begins. In many instances, a single NDS message may be sentfor each of the NDS windows 1902. An NDS message may be sent over anumber of channels, such as a predetermined number of channels, allchannels mentioned in a channel list, etc. An NDS message may be sent asa broadcast communication to neighbor devices.

An NDS message may generally advertise data regarding an operatingcontext that will be used by the LFD to receive a communication duringthe ND listening window 1904. For example, the NDS message may include achannel information element, schedule information element, timing andtype information element, seed information element, directed networkdiscovery information element, and so on regarding the operatingcontext. In one illustration, the LFD sends data regarding a unicastoperating context that indicates when the LFD will listen for unicastcommunications. In particular, the NDS message may include a channelinformation element that describes a channel plan, a generator function,and/or a list of channels to use during the ND listening window 1904.Further, the NDS message may include a schedule information element andtiming and type information element that describes a unicast schedule ofthe LFD, such as a schedule active period, a schedule repetitioninterval of a schedule element, and so on. In many instances, theschedule information element may not include event information, such asa reference schedule element boundary element number, an event offset,or an event repetition interval. The NDS message may also include adirected network discovery information element that describes the NDlistening window 1904 (e.g., describes the response period). Further,the NDS message may include a seed information element that indicates aseed value. Other information elements may also be included in the NDSmessage to advertise the operating context in which the LFD will beoperating during the listening window. Although the LFD in the aboveillustration sends data regarding a unicast operating context, in otherillustrations the LFD may send data regarding other types of operatingcontexts, such as a broadcast operating context, a multicast operatingcontext, etc. However, as noted above, in many instances data regardinga broadcast operating context is protected and is not provided untilafter authentication has occurred.

An FFD that receives the NDS message and decides to establish arelationship with the LFD (e.g., act as the parent), may use the data inthe NDS message to attempt to communicate with the LFD. In particular,the FFD may determine when the ND listening window 1904 is, and use thedata in the channel information element to frequency hop during the NDlistening window 1904. The LFD also frequency hops during the NDlistening window 1904 based on the same data. As such, during the NDlistening window 1904, the LFD and the FFD may frequency hop accordingto the same sequence.

In any event, the FFD sends an ND message during the ND listening window1904. The ND message may be sent as a unicast communication based on theunicast operating context of the LFD. In some instances, the FFD sendsthe ND message at a random time during the ND listening window 1904. TheND message may include data regarding any number of operating contexts.For example, the FFD may send data regarding a broadcast listeningschedule for the LFD, a unicast listening schedule for the LFD, abroadcast listening schedule of the FFD, a unicast listening schedule ofthe FFD, a broadcast listening schedule associated with groupacknowledgments, and so on. Although, as noted above, in many instancesdata regarding a broadcast listening schedule is protected and is notprovided until after authentication has occurred. These operatingcontexts may be used by the LFD in future communications with the FFD.For instance, based on a unicast listening schedule for the LFD, the LFDmay listen for communications from the FFD. In another instance, basedon a unicast listening schedule of the FFD, the LFD may determine whenit can send unicast communications to the FFD (e.g., determine when theFFD will be listening for the LFD). In some instances, an ND message mayalso include load balancing information for the FFD.

The LFD may receive ND messages from one or more FFDs during the NDlistening window 1904. The LFD may then select an FFD to act as a parentdevice. The LFD may select an FFD based on a variety of factors, such asan amount of load on an FFD, a proximity of the FFD (if known), astrength of a link between the devices, and so on. In some instances,the LFD may exchange test messages with the FFD over the link to gathermore reliable information about the link (e.g., more reliableinformation about a strength of the link).

Once an FFD is selected, the LFD may determine a sampled communicationschedule to implement. This may include referencing data provided in anND message regarding an operating context (e.g., referencing a scheduledescribed by the data). The LFD may then enter a low power state and/orawake from the low power state according to the sampled communicationschedule. For example, the LFD may awake to listen for a communicationat an event sampled listening reference point (SLRP).

In some instances, if an ND message is not received during the NDlistening window, the process 1900 may be repeated (e.g., send one ormore NDS messages and wait for another ND listening window). Here, theother ND listening window may be lengthened (or be the same, in someinstances) and/or the number of NDS messages that are sent may beincreased (or be the same, in some instances).

In some instances, the LFD may retain data in ND messages from FFDs fora period of time (e.g., until clocks drift out of synchronization). If,for example, a communication relationship with an initially selected FFDis not able to be established, the LFD may reference the data to selectanother FFD. In a similar manner, an FFD may retain data from the LFDfor a period of time, so that it may communicate with the LFD if the FFDis selected due to an initial failure to establish a communicationrelationship with a different FFD.

After a communication relationship is established between an LFD and anFFD, the LFD may operate according to the operating contexts that areestablished. Any change to an operating context may be communicated withan information element. For example, the FFD may update data for anoperating context by sending an information element that indicates anupdate to the operating context. The information element may include atag that identifies the operating context to update. As noted above, theinformation element may also reference data from another operatingcontext and/or include the data to be used to update the operatingcontext.

Example Information Elements

FIGS. 20-27 illustrate example information elements. In FIGS. 20-27, aninformation element may include one or more items (e.g., data). A numberof bits that represents each item is shown along the top of theinformation element. Although various items are shown as beingrepresented by a particular number of bits, such as one or more octets,any number of bits may be used to represent the various items. An itemthat is illustrated as including “0” bits or octets may indicate thatthe item is optional (e.g., may not be included in the informationelement in all instances). In one example, if an item is indicated asbeing represented by “Octets: 0/2,” this indicates that the item may notbe included, but is represented with two octets when included. Inanother example, if an item is indicated as being represented by“Octets: 0/Variable,” this indicates that the item may not be included,but is represented with a variable number of octets when included.Further, although items included in an information element areillustrated in a particular order, the items may be arranged in anyorder.

FIG. 20 illustrates an example channel information element (CH IE) 2000.As illustrated, the CH IE 2000 includes a WP sub-IE descriptor 2002,which represents a descriptor that is assigned to the CH IE 2000. Suchdescriptor 2002 may be defined according to a standard, such as theWi-SUN standard. The CH IE 2000 also include a tag 2004 indicating anoperating context for channel data referenced or included in the CH IE2000. Further, the CH IE 2000 includes a reference tag 2006 to (i)indicate whether the channel data is contained in the CH IE 2000 or hasbeen previously received and/or (ii) identify another operating contextassociated with previously received channel data to be used as thechannel data. For example, if the reference tag 2006 is set to “0,” thismay indicate that the channel data is included in the CH IE 2000.Alternatively, if the reference tag 2006 is set to a value, this mayindicate that the channel data has been previously received (e.g., thechannel data is associated with another operating context). Here, thevalue may identify the other operating context. In some instances, theCH IE 2000 also includes a future transition element number 2008 thatindicates when to apply the channel data to the operating contextidentified by the tag 2004. In many instances, the future transitionelement number 2008 may identify a schedule element. Although, in someinstances the future transition element number 2008 may identify achannel plan element.

In some instance, the CH IE 2000 may also include the channel data. Inparticular, the channel data may include and/or indicate a channel plan2010 (or channel plan type), a Pseudo-Random Generator function (PRG)2012 (also referred to as a generator function), an excluded channelcontrol 2014, and/or channel information 2016. The channel plan 2010 mayindicate whether data regarding a channel plan, channel spacing, and/ornumber of channel fields will be included in the CH IE 2000. The PRG2012 may indicate a generator function for generating a channel plan(e.g., direct hash, etc.) for the operating context identified by thetag 2004. The excluded channel control 2014 may indicate whether a listof excluded channels is included in the CH IE 2000. The channelinformation 2016 may include a regulatory domain field indicating aregulatory domain value, an operating class field indicating anoperating class value for the regulatory domain, a CHO field indicatinga frequency of a channel plan's channel 0, a channel spacing fieldindicating a spacing of a channel element in a channel plan, a number ofchannels field indicating a number of available channels in a channelplan (including any excluded channels), a fixed channel field indicatinga single channel from within a channel plan that is used fortransmitting, a channel hop count field indicating a number of channelsin a devices defined hop sequence, a channel hop list field indicatingchannels visited in a device's hop sequence (and/or an order of thechannels visited), an excluded channel ranges field indicating a rangeof channels that are not visited within a devices channel hop sequence(e.g., indicates channels that are excluded), an excluded channel maskfield indicating (for all channels within a device's channel hopsequence) those channels that are visited and those channels that arenot, and so on. In many instances, the information in the channelinformation 2016 may indicate a list of channels (e.g., a list ofavailable channels) and/or a channel plan.

FIG. 21 illustrates an example schedule information element (SCH IE)2100. As illustrated, the SCH IE 2100 includes a WP sub-IE descriptor2102, which represents a descriptor that is assigned to the SCH IE 2100.Such descriptor 2102 may be defined according to a standard, such as theWi-SUN standard. The SCH IE 2100 also includes a tag 2104 indicating anoperating context for schedule data referenced or included in the SCH IE2100. Further, the SCH IE 2100 includes a reference tag 2106 to (i)indicate whether at least a portion of the schedule data is contained inthe SCH IE 2100 and/or has been previously received and/or (ii) identifyanother operating context associated with a previously received scheduledata to be used as at least the portion of the schedule data. Forexample, if the reference tag 2106 is set to “0,” this may indicate thatthe schedule data is included in the SCH IE 2100. Alternatively, if thereference tag 2106 is set to a value, this may indicate that theschedule data has been previously received (e.g., the scheduled data isassociated with another operating context). Here, the value may identifythe other operating context. In some instances, the reference tag 2106may only reference a particular type of schedule data (e.g., a scheduleactive period and/or a schedule repetition interval). In otherinstances, the reference tag 2106 may reference any type of scheduledata.

In some instances, the SCH IE 2100 includes a future transition elementnumber 2108 that indicates when to apply the schedule data to theoperating context identified by the tag 2104. In many instances, thefuture transition element number 2108 may identify a schedule element.Although, in some instances the future transition element number 2108may identify a channel plan element.

In some instance, the SCH IE 2100 may also include the schedule data.The schedule data may include and/or indicate a schedule active period2110 comprising a duration of time of an active period within a scheduleelement during which a device listens for communications; a scheduleRepetition Interval (RI) 2112 comprising a duration of time of aschedule element; a reference Schedule Element Boundary (SEB) elementnumber 2114 comprising a schedule element number for a particularschedule element selected to serve as an event reference, where a startof the particular schedule element may comprise an event reference SEB;an event offset 2116 comprising a duration of time from the eventreference SEB to an event sampled listening reference point (SLRP);and/or an event RI 2118 comprising a duration of time between successiveevent SLRPs.

In some instance, the event offset 2116 and/or the event RI 2118 aresent only for a particular operating context (e.g., an LFD unicastoperating context and/or an LFD broadcast operating context). In otherinstances, the event offset 2116 and/or the event RI 2118 are sent forother operating contexts.

FIG. 22 illustrates an example Seed Information Element (Seed IE) 2200.As illustrated, the Seed IE 2200 includes a WP sub-IE descriptor 2202,which represents a descriptor that is assigned to the Seed IE 2200. Suchdescriptor 2202 may be defined according to a standard, such as theWi-SUN standard. The Seed IE 2200 also includes a tag 2204 indicating anoperating context for seed data referenced or included in the Seed IE2200. Further, the Seed IE 2200 includes a reference tag 2106 to (i)indicate whether the seed data is contained in the Seed IE 2200 or hasbeen previously received and/or (ii) identify another operating contextassociated with a previously received seed data to be used as the seeddata.

In some instances, the Seed IE 2200 includes a future transition elementnumber 2208 that indicates when to apply the seed data to the operatingcontext identified by the tag 2204. In many instances, the futuretransition element number 2208 may identify a schedule element.Although, in some instances the future transition element number 2208identifies a channel plan element.

In some instances, the Seed IE 2200 includes the seed data. The seeddata may comprise a seed 2210. The seed 2210 may indicate a seed valueto input into a generator function used to create a channel plan. Theseed value may comprise a random value, a predetermined value, a MACaddress, etc. In some instances, a particular operating context may beassociated with a particular seed value. That is, the particularoperating context may be implemented with the particular seed value. Ifinformation about the particular operating context is advertised, theparticular seed value may be advertised.

FIG. 23 illustrates an example Timing and Type Information Element (TTIE) 2300. As illustrated, the TT IE 2300 includes an IE descriptor 2302,which represents a descriptor that is assigned to the TT IE 2300. Suchdescriptor 2302 may be defined according to a standard, such as theWi-SUN standard. The TT IE 2300 also includes a sub ID 2304 thatrepresents an identifier for the TT IE 2300. Such sub ID 2304 may bedefined according to a standard, such as the Wi-SUN standard. Further,the TT IE 2300 indicates a frame type 2306 of a frame in which the TT IE2300 is contained. The frame type 2306 may indicate that the TT IE 2300is carried in an ND frame, an NDS frame, a LFD PAN Configuration (LPC)frame, and a LFD PAN Configuration Solicitation (LPCS) frame, a RadioFrequency (RF) test frame, or any other type of frame in which the TT IE2300 is carried.

Moreover, the TT IE 2300 includes a tag 2308 indicating an operatingcontext for timing data referenced or included in the TT IE 2300.Additionally, the TT IE 2300 may include an element 2310 that indicatesan element of a schedule (that is associated with the operating contextidentified by the tag 2308) in which the Frame Reference Time (FRT) of aframe carrying the TT IE 2300 falls. The FRT may refer to a referencepoint in the frame structure to which timing is referred. Further, theTT IE 2300 may include a Fractional Element Time (FET) 2312 (e.g., theportion of the element duration up to the FRT). In some instances, theFET 2312 may be defined as: FET=floor (((current time−elementSEB)*2{circumflex over ( )}16)/schedule RI), where all times are inmilliseconds, the event SEB is the SEB of the element 2310, and theschedule RI is the value of the RI of the schedule that is associatedwith the operating context identified by the tag 2308.

FIG. 24 illustrates an example Device Type Information Element (DTypeIE) 2400. The DType IE 2400 may provide information about a device typeand capabilities. In some instances, information in the DType IE 2400may be used to determine timing uncertainty associated with a device.

As illustrated, the DType IE 2400 includes a WP sub-IE descriptor 2402,which represents a descriptor that is assigned to the DType IE 2400.Such descriptor 2402 may be defined according to a standard, such as theWi-SUN standard. The DType IE 2400 also indicates a clock drift 2404 fora device (e.g., the device that sends the DType IE 2400). For example,the clock drift 2404 may represent a reporting device's worst drift of aclock that it uses to measure its frequency hopping dwell interval. TheDType IE 2400 may also indicate a timing accuracy 2406 of a device(e.g., the device that sends the DType IE 2400). For example, the timingaccuracy 2406 may indicate accuracy of time values generated by thedevice. Further, a reserved field 2408 of the DType IE 2400 may bereserved for various information. The DType IE 2400 may additionallyindicate a device type 2410 of a device that sends the DType IE 2400.The device type 2410 may indicate whether the device is a router (e.g.,border router), FFD, LFD, etc. As illustrated, the DType IE 2400 alsoindicates an LFD unicast latency 2412 comprising a maximum delay (e.g.,in milliseconds) before an available message received by the LFD parentis transmitted on the LFD unicast event. In some instances, the LFDunicast latency 2412 is present if the device type 2410 identifies anLFD.

FIG. 25 illustrates an example Group Acknowledgment Information Element(GACK IE) 2500. The GACK IE 2500 may be used to acknowledgecommunications from multiple devices.

As illustrated, the GACK IE 2500 includes a Nested WP IE Descriptor2502, which represents a descriptor that is assigned to the GACK IE2500. Such descriptor 2502 may be defined according to a standard, suchas the Wi-SUN standard. The GACK IE also includes a type field 2504, anumber field 2506 (e.g., number of acknowledgments), and a list field2508 (e.g., list of acknowledgments). The type field 2504 indicates atype of acknowledgements in the list field 2508. The number field 2506indicates a number of the acknowledgements in the list field 2508.Further, the list field 2508 includes a list of the acknowledgments.

Each acknowledgment in the list field 2508 may indicate that acommunication was received. An acknowledgment may generally include adevice identifier for a device that is being acknowledged (e.g., thedevice that sent a communication) and a communication identifier for thecommunication that is being acknowledged. The device identifier mayinclude a Medium Access Control (MAC) address of the device (e.g., 64bits), a hash of the MAC address of the device (e.g., 16 bits), or anyother data that may identify the device. The communication identifiermay include a sequence number of the communication (e.g., frame sequencenumber) (e.g., 8 bits), a Cyclic Redundancy Check (CRC) code for thecommunication, or any other data that may identify the communication. Insome instances, an acknowledgment may indicate a strength of a receivedsignal (e.g., Received Signal Level (RSL)) (e.g., 8 bits) for acommunication that is being acknowledged.

As noted above, each acknowledgment in the GACK IE 2500 may beassociated with a type. A type may indicate how an acknowledgment isrepresented, such as a format of the acknowledgment. For example, anacknowledgment may be represented as a first type—a MAC address (e.g.,64 bits) and a sequence number (e.g., 8 bits); a second type—a hash of aMAC address (e.g., 16 bits) and a sequence number; a third type—a MACaddress and a CRC code; a fourth type—a hash of a MAC address and a CRCcode, a sixth type—a MAC address, a sequence number, and a strength of areceived signal (e.g., RSL, which may be indicated with 8 bits oranother number of bits); a seventh type—a hash of a MAC address, asequence number, and an RSL; an eighth type—a combination of any of theabove noted types; so on. As such, acknowledgments may be represented indifferent formats (e.g., types), with some formats being longer (e.g.,including more bits) than other formats.

In one illustration, the type field 2504 of the GACK IE 2500 mayindicate that the list field 2508 is associated with acknowledgments ofthe first type noted above (e.g., a MAC address and a sequence number).The number field 2506 may indicate that three acknowledgments areincluded in the list field 2508. The three acknowledgments may be listedin the list field 2508 as: (1) a MAC address for a first device thatsent a first communication and a sequence number for the firstcommunication; (2) a MAC address for a second device that sent a secondcommunication and a sequence number for the second communication; and(3) a MAC address for a third device that sent a third communication anda sequence number for the third communication. In this illustration,each acknowledgment includes a combination of a MAC address and asequence number.

As shown in FIG. 25, the GACK IE 2500 may group acknowledgements bytype. That is, the type field 2504, the number field 2506, and the listfield 2508 may be associated with the same type of acknowledgments. Ifacknowledgments of a second, different type of acknowledgments areincluded in the GACK IE 2500, an additional type field, number field,and list field may be included. If acknowledgements of a third,different type of acknowledgments are included in the GACK IE 2500, afurther type field, number field, and list field may be included. Thismay be repeated for any number of types.

To illustrate, a first group of acknowledgments 2510 associated with afirst type may be included in a first continuous portion of the GACK IE2500. Further, a second group of acknowledgments 2512 associated with asecond type may be included in a second continuous portion of the GACKIE 2500. The first group of acknowledgments 2510 may begin with the typefield 2504 indicating that the acknowledgments in the list field 2508are each of the first type. Further, the second group of acknowledgments2512 may begin with a type field 2514 indicating that theacknowledgments in a list field 2516 are each of the second type. Anumber field 2518 may indicate a number of the acknowledgments in thelist field 2516. As such, the first portion of the GACK IE 2500 includesa single field (the field 2504) to indicate the first type ofacknowledgements in the list field 2508 and the second portion of theGACK IE 2500 includes a single field (the field 2514) to indicate thesecond type of acknowledgements in the list field 2516.

Although various items are shown in the GACK IE 2500 to indicatespecific information, any of the items may be used to indicateinformation. For example, the descriptor 2502 may be used in someinstances to indicate information of the fields 2504, 2506, and/or 2508.For example, the descriptor 2502 may indicate that all acknowledgmentsin the GACK IE 2500 are associated with a particular type. Here, thetype field 2504 may be eliminated.

FIG. 26 illustrates an example Load Balancing Information Element (LBIE) 2600. The LB IE 2600 may be used to send information regarding anamount of load on a device. For example, the LB IE 2600 may provideinformation regarding a current number of FFDs and/or LFD devices routedby a transmitting device.

As illustrated, the LB IE 2600 includes a WP sub-IE Descriptor 2602,which represents a descriptor that is assigned to the LB IE 2600. Suchdescriptor 2602 may be defined according to a standard, such as theWi-SUN standard. The LB IE 2600 also includes a number of FFDs field2604 that indicates a number of 1-hop neighbors for which a device isacting as a router. In other words, the number of FFDs field 2604 mayindicate how many FFD neighbors are heard through a direct link.Further, the LB IE 2600 includes a number of LFDs field 2608 thatindicates a number of children devices for which a device is currentlyacting as a parent (e.g., a number of children LFDs that an FFD issupporting).

Although not illustrated in FIG. 26, in some instances the LB IE 2600may additionally, or alternatively, indicate other information regardinga load on a device, such as a processor load of the device (e.g., anaverage processor load, a current processor load, etc.), a radio load onthe device (e.g., how much of the time the radio is being used), and soon.

FIG. 27 illustrates an example Directed Network Discovery InformationElement (DND IE) 2700. In some instances, the DND IE 2700 may be usedduring discovery to provide information regarding a listening window.The DND IE 2700 may also include information to quality a potential FFDto be able to reply.

As illustrated, the DND IE 2700 includes a WP sub-IE Descriptor 2702,which represents a descriptor that is assigned to the DND IE 2700. Suchdescriptor 2702 may be defined according to a standard, such as theWi-SUN standard. The DND IE 2700 also includes a rank field 2704 thatindicates a rank value (e.g., maximum value) permitted for a recipientof the DND IE 2700 to respond. In one example, the rank field 2704 mayspecify the maximum permitted rank an FFD may have in order to bepermitted to reply. Further, the DND IE 2700 includes a responsethreshold field 2706 that indicates a value of a minimum LQI level atwhich a frame carrying the DND IE 2700 is received to permit a response.In one example, the response threshold field 2706 may specify a minimumsignal quality with which the frame carrying the DND IE 2700 is receivedby an FFD in order for the FFD to be permitted to reply. The DND IE 2700also includes a response interval field 2708 that indicates a time(e.g., in milliseconds) from a Frame Reference Time (FRT) of a framecarrying the DND IE 2700 at which a device will begin to listen forresponses. In other words, the response interval field 2708 may indicatewhen a Network Discovery (ND) listening window may begin. Moreover, theDND IE 2700 includes a response period field 2710 that indicates a time(e.g., in milliseconds) during which a device will listen for responses.In other words, the response period field 2710 may indicate a durationof time of an ND listening window.

Information Element Chart

FIG. 28 illustrates a chart 2800 that indicates examples when variousinformation elements may be used. The chart 2800 illustrates just someof the many instances where the information elements may be included. Inother instances, the information elements may be used in other contexts.Further, the chart 2800 includes a few of the many types of informationelements. As such, other types of information elements may be includedin the frames.

In the chart 2800, an “X” indicates that an information element isincluded in a frame. In some instances, the “X” indicates a requirementto include the information element, while in other instances the “X”indicates that the information element may be included, if needed.Although the chart 2800 indicates that certain frames include certaininformation elements, in other instances an information element may beincluded in any type of frame.

In the chart 2800, different types of frames are indicated across thetop (excluding the “Order” identifier), while different type ofInformation Elements (IEs) are indicated on a second column from theleft. A “frame” in many instances herein may be referred to as a“message.” As noted above, the chart 2800 may identify the IEs that areincluded in a frame. For example, a Network Discovery Solicitation “NDS”frame may include a Timing and Type (TT) IE, a Channel (CH) IE, aDirected Network Discovery (DND) IE, a Device Type (DType) IE, aSchedule (SCH) IE, and a Seed IE. An ND frame may include a TT IE, a CHIE, a DType IE, a SCH IE, and a Seed IE. An LFD PAN ConfigurationSolicitation (LPCS) frame may include a TT IE and a SCH IE. An LFD PANConfiguration (LPC) frame may include a TT IE, a CH IE, and a SCH IE. AData frame may include a TT IE and a SCH IE. In many instances, the NDSand ND frames may be sent during discovery, as discussed herein. TheLPCS and LPC frames may be sent during PAN configuration. The Data framemay be sent any time data is to be exchanged.

In some instances, a frame may include multiple IEs of the same type.For instance, an ND frame may include a first set of IEs for a firstoperating context (e.g., a CH IE, SCH IE, and Seed IE for the firstoperating context) and a second set of IEs for a second operatingcontext (e.g., a CH IE, SCH IE, and Seed IE for the second operatingcontext). If the first operating context and the second operatingcontext are to be implemented with the same data (e.g., the same channelplan or same schedule), the second set of IEs may reference data in thefirst set of IEs.

As also illustrated in FIG. 28, an “Order” column indicates a precedencethat an IE takes relative to other IEs of the same type (e.g., WH-IE orWP-sub-IE). A lower number may indicate a higher precedence (e.g., thatthe IE is positioned first in the frame). For example, a DND IE or DTypeIE may be included first in a frame over a CH IE.

1-14. (canceled)
 15. A device comprising: a radio configured to: receivea first communication from a first node, the first node having a firstparent-child relationship with the device; receive a secondcommunication from a second node, the second node having a secondparent-child relationship with the device; and broadcast, to the firstnode and the second node, a group acknowledgement message acknowledgingreceipt of the first communication and the second communication; one ormore processors communicatively coupled to the radio; and memorycommunicatively coupled to the one or more processors, the memorystoring one or more instructions that, when executed by the one or moreprocessors, cause the one or more processors to perform operationscomprising: generating the group acknowledgement message, the groupacknowledgement message including: a first acknowledgement indicatingthat the first communication was received at the device from the firstnode, the first acknowledgment including a first communicationidentifier for the first communication and a first device identifier forthe first node; and a second acknowledgement indicating that the secondcommunication was received at the device from the second node, thesecond acknowledgment including a second communication identifier forthe second communication and a second device identifier for the secondnode.
 16. The device of claim 15, wherein the first node and the secondnode are children to the device, and wherein the operations furthercomprise: determining that a first short device identifier for the firstnode and a second short device identifier for the second node are thesame; and based at least in part on determining that the first shortdevice identifier for the first node and the second short deviceidentifier for the second node are the same, determining to use a firstlong device identifier for the first node and a second long deviceidentifier for the second node, the first long device identifier for thefirst node being longer than the first short device identifier for thefirst node and the second long device identifier for the second nodebeing longer than the second short device identifier for the secondnode, wherein the device identifier for the first node comprises thefirst long device identifier for the first node and the deviceidentifier for the second node comprises the second long deviceidentifier for the second node.
 17. The device of claim 15, wherein thegenerating the group acknowledgment message includes groupingacknowledgments in the group acknowledgment message by type, the typeindicating how the acknowledgments are represented, the acknowledgmentsincluding the first acknowledgment and the second acknowledgment. 18.The device of claim 17, wherein each group of acknowledgements of a typeare indicated in the group acknowledgement message with a single typefield.
 19. The device of claim 15, wherein the first node comprises afirst battery powered device and the second node comprises a secondbattery powered device.
 20. The device of claim 15, wherein the groupacknowledgement message indicates a first signal strength of receivingthe first communication and a second signal strength of receiving thesecond communication.
 21. A method of acknowledging communications, themethod comprising: with a transceiver: receiving a first communicationfrom a first node, the first node having a first parent-childrelationship with a device; receiving a second communication from asecond node, the second node having a second parent-child relationshipwith the device; and broadcasting, to the first node and the secondnode, a group acknowledgement message acknowledging receipt of the firstcommunication and the second communication; with one or more processorscommunicatively coupled to the transceiver and executing one or moreinstructions stored in a memory communicatively coupled to the one ormore processors: generating the group acknowledgement message, the groupacknowledgement message including: a first acknowledgement indicatingthat the first communication was received at the device from the firstnode, the first acknowledgment including a first communicationidentifier for the first communication and a first device identifier forthe first node; and a second acknowledgement indicating that the secondcommunication was received at the device from the second node, thesecond acknowledgment including a second communication identifier forthe second communication and a second device identifier for the secondnode.
 22. The method of claim 21, further comprising determining thatthe first communication was received by at least one of the first nodeand the second node based at least in part on the group acknowledgementmessage.
 23. The method of claim 21, wherein the group acknowledgementmessage includes: a type field to indicate a device identifier formatand a communication identifier format for acknowledgments in a list ofacknowledgements, a number field to indicate a number of theacknowledgements in the list of acknowledgements, and a list field thatincludes the acknowledgements in the list of acknowledgements, the listfield including the first acknowledgement and the secondacknowledgement.
 24. The method of claim 21, wherein: the firstcommunication identifier for the first communication comprises at leastone of a first sequence number of the first communication or a firstCyclic Redundancy Check (CRC) code for the first communication, thefirst device identifier for the first node comprising at least one of afirst Medium Access Control (MAC) address of the first node or a firsthash of the first MAC address of the first node; and the secondcommunication identifier for the second communication comprising atleast one of a second sequence number of the second communication or asecond CRC code for the second communication, the second deviceidentifier for the second node comprising at least one of a second MACaddress of the second node or a second hash of the MAC address of thesecond node.
 25. The method of claim 21, wherein, wherein the first nodeand the second node are children to the device, and wherein the methodfurther comprises: determining that a first short device identifier forthe first node and a second short device identifier for the second nodeare the same; and based at least in part on determining that the firstshort device identifier for the first node and the second short deviceidentifier for the second node are the same, determining to use a firstlong device identifier for the first node and a second long deviceidentifier for the second node, the first long device identifier for thefirst node being longer than the first short device identifier for thefirst node and the second long device identifier for the second nodebeing longer than the second short device identifier for the secondnode, wherein the first device identifier for the first node comprisesthe first long device identifier for the first node and the seconddevice identifier for the second node comprises the second long deviceidentifier for the second node.
 26. The method of claim 21, wherein,wherein the generating the group acknowledgment message includesgrouping acknowledgments in the group acknowledgment message by type,the type indicating how the acknowledgments are represented, theacknowledgments including the first acknowledgment and the secondacknowledgment.
 27. The method of claim 26, wherein each group ofacknowledgements of a type are indicated in the group acknowledgementmessage with a single type field.
 28. The method of claim 21, whereinthe first node comprises a first battery powered device and the secondnode comprises a second battery powered device.
 29. The method of claim21, wherein the group acknowledgement message indicates a first signalstrength of receiving the first communication and a second signalstrength of receiving the second communication.
 30. One or morecomputer-readable storage media storing computer-readable instructionsthat, when executed, instruct a processing unit to perform operationscomprising: with a transceiver: receiving a first communication from afirst node, the first node having a first parent-child relationship witha device; receiving a second communication from a second node, thesecond node having a second parent-child relationship with the device;and broadcasting, to the first node and the second node, a groupacknowledgement message acknowledging receipt of the first communicationand the second communication; with one or more processorscommunicatively coupled to the transceiver and executing one or moreinstructions stored in a memory communicatively coupled to the one ormore processors: generating the group acknowledgement message, the groupacknowledgement message including: a first acknowledgement indicatingthat the first communication was received at the device from the firstnode, the first acknowledgment including a first communicationidentifier for the first communication and a first device identifier forthe first node; and a second acknowledgement indicating that the secondcommunication was received at the device from the second node, thesecond acknowledgment including a second communication identifier forthe second communication and a second device identifier for the secondnode.
 31. The one or more computer-readable storage media of claim 30,wherein the first node and the second node are children to the device,and wherein the operations further comprise: determining that a firstshort device identifier for the first node and a second short deviceidentifier for the second node are the same; and based at least in parton determining that the first short device identifier for the first nodeand the second short device identifier for the second node are the same,determining to use a first long device identifier for the first node anda second long device identifier for the second node, the first longdevice identifier for the first node being longer than the first shortdevice identifier for the first node and the second long deviceidentifier for the second node being longer than the second short deviceidentifier for the second node, wherein the first device identifier forthe first node comprises the first long device identifier for the firstnode and the second device identifier for the second node comprises thesecond long device identifier for the second node.
 32. The one or morecomputer-readable storage media of claim 31, wherein the generating thegroup acknowledgment message includes grouping acknowledgments in thegroup acknowledgment message by type, the type indicating how theacknowledgments are represented, the acknowledgments including the firstacknowledgment and the second acknowledgment.
 33. The one or morecomputer-readable storage media of claim 31, wherein each group ofacknowledgements of a type are indicated in the group acknowledgementmessage with a single type field.
 34. The one or more computer-readablestorage media of claim 31, wherein the first node comprises a firstbattery powered device and the second node comprises a second batterypowered device.